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/repairgit 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/repair)<a href="https://agentmods.dev/commands/xiaolai/cc-suite/repair"><img src="https://agentmods.dev/badge/commands/xiaolai/cc-suite/repair.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.00057 | $0.00842 |
| Opus 5 | $0.00028 | $0.00421 |
| Sonnet 5 | $0.00011 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
repair 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC-Suite Repair
Re-run every cc-suite setup script in sequence, non-interactively. All scripts are idempotent — existing correct artifacts are left alone; missing or broken ones are (re)created.
Use this as the escalation step after /cc-suite:diagnose has tried targeted fixes and issues remain. If repair also fails, the next step is /cc-suite:init (full interactive re-initialization).
Workflow
Step 1: Run bridge init
Creates AGENTS.md, CLAUDE.md (@AGENTS.md), Codex scaffolding, the
.agents/skills bridge, and the generated .agents/mcp_config.json projection.
Antigravity CLI (agy) reads AGENTS.md natively and uses .agents/ workspace
assets; no new Gemini-era project files are created.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/init.sh"
Step 2: Expose skills
Links plugin skills into .claude/skills/cc-suite/ and creates .agents/skills → ../.claude/skills.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_skills.sh"
Step 3: Register codex-cli MCP server
Adds codex-cli to .mcp.json so Claude can invoke Codex as a tool.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/mcp_codex.sh"
Step 4: Register claude-code MCP server
Adds claude-code (claude-octopus) to .codex/config.toml so Codex can invoke Claude as a tool.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/mcp_claude.sh"
Step 5: Mirror MCP servers
Copies MCP servers from .mcp.json into .codex/config.toml and
.agents/mcp_config.json so Codex and agy can see the full project MCP surface.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_mcp.sh"
Step 6: Bridge hooks (if applicable)
Mirrors .claude/settings.json hooks into .codex/hooks.json. Skips gracefully if there are no hooks to bridge.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/bridge_hooks.py"
Step 7: Bridge advisor agents (if applicable)
Re-registers any cc-suite advisor agents declared in .cc-suite/agents/*.md. No-op if the directory doesn't exist.
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.
- 4d ago First seen · 94 lines · 57 tokens per session scan A 079c3881d322
repair is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 2d ago), licensed ISC. It adds 57 tokens to every session and 842 once invoked, about $0.0003 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.