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/kaitranntt/ccs/ccsgit clone --depth 1 https://github.com/kaitranntt/ccsWrote 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/kaitranntt/ccs/ccs)<a href="https://agentmods.dev/commands/kaitranntt/ccs/ccs"><img src="https://agentmods.dev/badge/commands/kaitranntt/ccs/ccs.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.00012 | $0.00160 |
| Opus 5 | $0.00006 | $0.00080 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
ccs 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.
What it actually says
Activate ccs-delegation skill. The skill contains all execution logic.
Task: Parse $ARGUMENTS, select optimal profile from ~/.ccs/config.json, enhance prompt, execute delegation via CCS CLI.
Examples:
/ccs "refactor auth.js to use async/await" # Simple task
/ccs "analyze entire architecture" # Long-context task
/ccs "think about caching strategy" # Reasoning task
/ccs --glm "add tests for UserService" # Force specific profile
/ccs "/cook create landing page" # Nested slash command
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 · 18 lines · 12 tokens per session scan A cf9bd6e0e170
ccs is a command published in the GitHub repository kaitranntt/ccs (2,834 stars, last pushed 7d ago), licensed MIT. It adds 12 tokens to every session and 160 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
workflow-from-spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern.
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
containers
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.