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/sync-mcpgit clone --depth 1 https://github.com/xiaolai/cc-suiteWhat 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.00461 |
| Opus 5 | $0.00009 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
sync-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 3d 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:sync-mcp
Synchronize the project MCP servers Claude Code reads from .mcp.json into
Codex's .codex/config.toml and Antigravity's .agents/mcp_config.json.
This is the explicit Claude → Codex/agy MCP sync command. It is equivalent to
/cc-suite:bridge-mcp; keep both names available because bridge-mcp is the
historical command name.
Workflow
Step 1: Run the sync script
bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_mcp.sh"
The script skips codex-cli only in Codex's own config; agy may use it to call
Codex. It also adds the pinned claude-code server to agy's projection so agy
can call Claude. It normalizes Claude server names only in the Codex projection to
Codex's ^[a-zA-Z0-9_-]+$ grammar and
converts remote url/httpUrl fields to agy's serverUrl. Secret values are
never copied into .codex/config.toml; the generated agy config is ignored by
default because MCP definitions can preserve environment values and local paths.
If .agents/mcp_config.json exists without cc-suite provenance, the bridge
refuses to overwrite it. Merge the desired entries manually or remove the
user-owned file only after confirming it is safe to do so.
If the script exits non-zero, report the error and stop. If .mcp.json is
missing, report: No .mcp.json found — nothing to sync.
Step 2: Report the result
Report the source name, Codex name, and action for every server:
| Claude name | Codex name | Action |
|---|---|---|
{server-name} |
{codex-name} |
synced / already present / skipped |
Tell the user to restart Codex or agy if either was already running; both load project MCP configuration at session start.
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.
- 3d ago First seen · 49 lines · 17 tokens per session scan A 275133b6c1f9
sync-mcp is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 24d ago), licensed ISC. It adds 17 tokens to every session and 461 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.