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/list-agentsgit 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/list-agents)<a href="https://agentmods.dev/commands/xiaolai/cc-suite/list-agents"><img src="https://agentmods.dev/badge/commands/xiaolai/cc-suite/list-agents.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.00026 | $0.00774 |
| Opus 5 | $0.00013 | $0.00387 |
| Sonnet 5 | $0.00005 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
list-agents 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC-Suite List Agents
Show the user every advisor agent declared in .cc-suite/agents/, with the information they'd need to know which one to consult.
Workflow
Step 1: Check that the directory exists
ls .cc-suite/agents/ 2>/dev/null
If .cc-suite/agents/ doesn't exist or contains no .md files, tell the user:
No advisor agents in this project.
To add one, run `/cc-suite:add-agent <preset>` — available presets:
- north_star_advisor — project's overarching priorities
- clarity_reviewer — readability over correctness
- simplicity_advocate — smallest complete solution
- security_skeptic — adversarial reviewer
- deletion_advocate — finds removable code
- documentation_critic — judges doc honesty + audience fit
Or `/cc-suite:add-agent --custom` to write one from scratch.
Stop here.
Step 2: Parse each agent file
For each .cc-suite/agents/*.md, extract from frontmatter:
name(or filename stem if not declared)descriptiontool_name(or<name>_consultif not declared)model(or "default" if not declared)allowed_tools(or default[Read, Grep, Glob])cwd(or "." if not declared)max_turns,max_budget_usd
Step 3: Render the report
## Project advisors (N total)
| Agent | Consult tool | Model | Scope | Description |
|---|---|---|---|---|
| `<name>` | `mcp__<name>__<tool_name>` | <model> | <cwd> | <description> |
| ... | ... | ... | ... | ... |
### Details
#### <name>
- **Tools**: <allowed_tools>
- **Max turns**: <max_turns>
- **Budget cap**: $<max_budget_usd> per consultation
- **Timeline**: `.cc-suite/agents/<name>/timeline/` (gitignored by default)
- **File**: `.cc-suite/agents/<name>.md`
(Repeat per agent.)
### Status
- Bridge script: `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/bridge_agents.py` — run after editing any file above
- Registrations live in: `.mcp.json` (Claude side), `.codex/config.toml` (Codex side), and the generated `.agents/mcp_config.json` projection for agy
- Restart Claude Code if you just added or removed an agent
- Run `/cc-suite:bridge-mcp` after adding or editing an agent if agy should see it
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 · 98 lines · 26 tokens per session scan A 46c8ac7430a3
list-agents is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 25d ago), licensed ISC. It adds 26 tokens to every session and 774 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.