Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/xiaolai/cc-suite/bridge-mcpgit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/xiaolai/cc-suite/bridge-mcp)<a href="https://agentmods.dev/commands/xiaolai/cc-suite/bridge-mcp"><img src="https://agentmods.dev/badge/commands/xiaolai/cc-suite/bridge-mcp.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00017 | $0.00394 |
| Opus 5 | $0.00009 | $0.00197 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
bridge-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/cc-suite:bridge-mcp
Copy every MCP server registered in .mcp.json into both target projections:
Codex's .codex/config.toml and Antigravity's generated
.agents/mcp_config.json. The agy projection also registers the pinned
claude-code server for agy → Claude delegation.
Idempotent and reconciliatory. Codex entries are sentinel-managed and stale
cc-suite-owned entries are removed when they disappear from .mcp.json. Agy
entries are refreshed only when the provenance file belongs to cc-suite;
user-managed agy configs are never overwritten. Names containing characters Codex rejects (for example,
@scope/pkg) are normalized only in the Codex projection.
The explicit alias /cc-suite:sync-mcp runs the same sync for discoverability.
Workflow
Step 1: Run the bridge script
bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_mcp.sh"
If the script exits non-zero, report the error output and stop. If .mcp.json
does not exist, Codex receives no project servers; the agy projection still
contains cc-suite's reverse Claude bridge.
Step 2: Report results
Use this template:
**bridge-mcp**: MCP servers mirrored from `.mcp.json` to Codex and agy
| Server | Action |
|--------|--------|
| {server-name} | mirrored |
| {server-name} | already present (skipped) |
| codex-cli | available to agy; skipped in Codex's own config |
Success criterion: script exits 0 and the source servers appear in both target configs, subject to transport validation and user-managed conflict protection.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 50 lines · 17 tokens per session scan A 1a8239d2c693
bridge-mcp is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 3d ago), licensed ISC. It adds 17 tokens to every session and 394 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.