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/continuegit clone --depth 1 https://github.com/kaitranntt/ccsWhat 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.00136 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
continue 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.
What it actually says
Activate ccs-delegation skill. The skill contains all execution logic.
Task: Detect last-used profile from ~/.ccs/delegation-sessions.json, parse $ARGUMENTS, enhance with previous context, execute continuation via CCS CLI.
Examples:
/ccs:continue "also update the examples section" # Use last profile
/ccs:continue --glm "add unit tests" # Switch profiles
/ccs:continue "/commit with message" # 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.
- 2d ago First seen · 16 lines · 11 tokens per session scan A 3f15cd527d3c
continue is a command published in the GitHub repository kaitranntt/ccs (2,834 stars, last pushed 6d ago), licensed MIT. It adds 11 tokens to every session and 136 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.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
research_codebase
Document codebase as-is with thoughts directory for historical context.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.