Skip to content

hashgraph-online/awesome-codex-plugins / plugins/bindryai/Plugins/skills/bindry-connect

bindry-connect

Verified

One-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.

FileKindSize
SKILL.mdskill md2.0 KB
---
name: bindry-connect
description: One-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.

1. Explain up front: this needs an API key — the same one already used for pinned `bindry-sync` works 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 a `BINDRY_API_TOKEN` environment variable rather than pasting it directly.
2. Need `--api-base <url>` (the Bindry API's base URL — ask if not obvious from context, e.g. from an existing
   `bindry.config.json` in a project this user has already synced).
3. 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
   ```
4. 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).
5. Once connected, tell the user live-mode skills are ready to use — syncing a Binder with `--mode live` will now
   compile skills the agent can actually call MCP tools through, and the `bindry-check` skill will report them
   as "live (always current)" rather than stale or unknown.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall