hashgraph-online/awesome-codex-plugins / plugins/bindryai/Plugins/skills/bindry-connect
bindry-connect
UnverifiedOne-time setup connecting Codex to the Bindry MCP server, for live-mode skills. Use when the user wants to enable live mode for Bindry skills or asks to connect Codex to Bindry's MCP server.
Connect this machine to the Bindry MCP server so --mode live skills (compiled by the bindry-sync skill)
actually work. This is a one-time, per-machine/user step — it isn't tied to any particular project or Binder,
and only needs to happen once even if the user syncs several Binders live later.
- Explain up front: this needs an API key — the same one already used for pinned
bindry-syncworks here too, no separate scope or permission to grant. Generate one from the workspace's team page in Bindry (not Account settings — a key is scoped to whichever workspace's team page made it). Recommend the user put it in aBINDRY_API_TOKENenvironment variable rather than pasting it directly. - Need
--api-base <url>(the Bindry API's base URL — ask if not obvious from context, e.g. from an existingbindry.config.jsonin a project this user has already synced). - This changes standing local CLI configuration (adds an MCP server to this machine's Codex config) — state
the exact command below and get explicit confirmation before running it, don't run it silently:
codex mcp add bindry --url <api-base>/api/mcp --bearer-token-env-var BINDRY_API_TOKEN - After running it, confirm the server shows as connected (list configured MCP servers and check
bindry's status). If it reports a connection failure, report exactly what it said (bad API base, network issue, or an invalid/expired key show up as different failures — don't guess which without checking). - Once connected, tell the user live-mode skills are ready to use — syncing a Binder with
--mode livewill now compile skills the agent can actually call MCP tools through, and thebindry-checkskill will report them as "live (always current)" rather than stale or unknown.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |