CCS is a command-line manager that lets users switch among AI coding runtimes, provider accounts, and model profiles through one interface. It is for developers who use Claude Code or compatible CLIs and need to change accounts or backends without repeatedly editing configuration.
Borrowing it
Nothing to install: this file belongs to kaitranntt/ccs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaitranntt/ccs/main/.claude/skills/ccs-delegation/SKILL.mdgit 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/skills/kaitranntt/ccs/ccs-delegation)<a href="https://agentmods.dev/skills/kaitranntt/ccs/ccs-delegation"><img src="https://agentmods.dev/badge/skills/kaitranntt/ccs/ccs-delegation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kaitranntt/ccs/ccs-delegation"><img src="https://agentmods.dev/badge/skills/kaitranntt/ccs/ccs-delegation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00102 | $0.01887 |
| Opus 5 | $0.00051 | $0.00944 |
| Sonnet 5 | $0.00020 | $0.00377 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
ccs-delegation 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ccs-delegation — 98% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCS Delegation
Delegate deterministic tasks to cost-optimized models via CCS CLI.
Core Concept
Execute tasks via alternative models using:
- Initial delegation:
ccs {profile} -p "task" - Session continuation:
ccs {profile}:continue -p "follow-up"
Profile Selection:
- Auto-select from
~/.ccs/config.jsonvia task analysis - Profiles: glm (cost-optimized), kimi (long-context/reasoning), custom profiles
- Override:
--{profile}flag forces specific profile
User Invocation Patterns
Users trigger delegation naturally:
- "use ccs [task]" - Auto-select best profile
- "use ccs --glm [task]" - Force GLM profile
- "use ccs --kimi [task]" - Force Kimi profile
- "use ccs:continue [task]" - Continue last session
Examples:
- "use ccs to fix typos in README.md"
- "use ccs to analyze the entire architecture"
- "use ccs --glm to add unit tests"
- "use ccs:continue to commit the changes"
Agent Response Protocol
For /ccs [task]:
-
Parse override flag
- Scan task for pattern:
--(\w+) - If match:
profile = match[1], remove flag from task, skip to step 5 - If no match: continue to step 2
- Scan task for pattern:
-
Discover profiles
- Read
~/.ccs/config.jsonusing Read tool - Extract
Object.keys(config.profiles)→availableProfiles[] - If file missing → Error: "CCS not configured. Run: ccs doctor"
- If empty → Error: "No profiles in config.json"
- Read
-
Analyze task requirements
- Scan task for keywords:
/(think|analyze|reason|debug|investigate|evaluate)/i→needsReasoning = true/(architecture|entire|all files|codebase|analyze all)/i→needsLongContext = true/(typo|test|refactor|update|fix)/i→preferCostOptimized = true
- Scan task for keywords:
-
Select profile
- For each profile in
availableProfiles: classify by name pattern (see Profile Characteristic Inference table) - If
needsReasoning: filter profiles wherereasoning=true→ prefer kimi - Else if
needsLongContext: filter profiles wherecontext=long→ prefer kimi - Else: filter profiles where
cost=low→ prefer glm selectedProfile = filteredProfiles[0]- If
filteredProfiles.length === 0: fallback toglmif exists, else first available - If no profiles: Error
- For each profile in
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 196 lines · 102 tokens per session scan A bb80e0c40d80
ccs-delegation is a skill published in the GitHub repository kaitranntt/ccs (2,841 stars, last pushed 13d ago), licensed MIT. It adds 102 tokens to every session and 1,887 once invoked, about $0.0005 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 skills, from other repositories
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
cli-resilience
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
9router-web-fetch
Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Ollama Cloud / Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
9router-web-search
Web and X search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity / Xquik. Use when the user wants to search the web, find articles, or search public X posts.
9router-embeddings
Generate vector embeddings via 9Router /v1/embeddings using OpenAI / Gemini / Mistral / Voyage / Nvidia / GitHub embedding models for RAG, semantic search, similarity. Use when the user wants embeddings, vectors, RAG, semantic search, or to embed text.