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/setupgit 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.00011 | $0.00741 |
| Opus 5 | $0.00005 | $0.00370 |
| Sonnet 5 | $0.00002 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
setup 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Workflow
Step 1: Parse flags
| Flag | Action |
|---|---|
--enable-review-gate |
Enable the stop-time review gate, then show status |
--disable-review-gate |
Disable the stop-time review gate, then show status |
| (empty) | Just show current status |
If enabling the review gate, display a warning first:
WARNING: The stop-time review gate will run a Codex adversarial review every time
you end a session. This can:
- Add 1-5 minutes to session end
- Use Codex API credits
- Block session end if issues are found
This creates a Claude→Codex review loop that catches issues but increases usage.
Use AskUserQuestion with "Enable" and "Cancel" options.
Step 2: Update review gate config
If the user chose to enable:
node -e "
const { setConfig } = await import('${CLAUDE_PLUGIN_ROOT}/scripts/lib/state.mjs');
setConfig(process.cwd(), 'stopReviewGate', true);
console.log('Review gate enabled.');
"
If the user chose to disable:
node -e "
const { setConfig } = await import('${CLAUDE_PLUGIN_ROOT}/scripts/lib/state.mjs');
setConfig(process.cwd(), 'stopReviewGate', false);
console.log('Review gate disabled.');
"
Step 3: Run readiness checks
Check each prerequisite:
- Node.js:
node --version(required >= 18.18.0) - Codex CLI:
codex --version - Authentication:
codex login status
Antigravity is an independent optional backend. When Google-backed delegation is
needed, run /cc-suite:agy-preflight separately; it checks agy, Google
authentication, model discovery, and the workspace MCP projection. This setup
command does not substitute the deprecated consumer Gemini CLI.
Step 4: Display status report
# Codex Toolkit Setup
Status: {ready / needs attention}
Checks:
- node: {version or "not found"}
- codex CLI: {version or "not found — install: npm install -g @openai/codex"}
- auth: {status or "not authenticated — run: ! codex login"}
- review gate: {enabled / disabled}
{Next steps if any checks failed}
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.
- 2d ago First seen · 107 lines · 11 tokens per session scan A 3e2aa7f20e69
setup is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 23d ago), licensed ISC. It adds 11 tokens to every session and 741 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.