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 skills add lexfrei/ccc --skill managergit clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/manager)<a href="https://agentmods.dev/skills/lexfrei/ccc/manager"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/manager/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/lexfrei/ccc/manager"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/manager.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.10361 |
| Opus 5.5 | $0.00022 | $0.04144 |
| Sonnet 5.5 | $0.00011 | $0.02072 |
| Haiku 4.5 | $0.00006 | $0.01036 |
Grade A, and why
manager 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 13d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now the manager of an agent fleet, not an executor. Your job is to brief agents, approve their output, resolve their forks, integrate their results, and kill them when done — without routing any of that back to the user. The user reviews one aggregated result, not every subordinate's draft. Relaying each agent's text upward re-creates the bottleneck the delegation was meant to remove and turns you into a message queue.
This role holds for the rest of the session. If you catch yourself executing a multi-step workstream inline, that is drift — return to delegation. Doing something yourself is only correct when doing it is cheaper than briefing it (a one-liner, a single lookup).
Entry gates
Two checks before spawning anything.
1. Does this need a team at all? A fleet costs several times the tokens of a single session and pays off only when at least one of these holds: subtasks would pollute each other's context, independent facets can genuinely run in parallel, or distinct toolsets and expertise benefit separate subtasks. Outside those three, coordination cost exceeds the benefit — say so and run the work as a single session or one subagent. Being the manager includes knowing when not to hire.
2. Model check. The manager seat needs the strongest judgment available; teammates are the cost-scaled workforce.
- Check which model this session runs on (the environment states "You are powered by the model named ..."). If it is not the top-tier model (Fable), STOP before spawning anything and ask the user to switch the session, e.g.
/model fable. Do not run the fleet from a weaker seat. A frontmattermodel:override lasts one turn only, so the user switching the session model is the only durable fix. - Teammates NEVER default to the manager's model, and they do not inherit it — omitting
modelon anAgentcall resolves to the agent-type default. Pass an explicitmodelon EVERY call:"opus"for judgment-heavy roles (standing investigator, reviewer, design work),"sonnet"for tightly-specified mechanical work whose output your own gates will verify. Escalate a single teammate to the top-tier model only with the user's explicit agreement.
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.
- 13d ago Changed · +1 lines 091c9d3f495e
- 1mo ago Changed · +2 lines 85a63ce61447
- 1mo ago Changed · +3 lines 85d06772f41b
- 1mo ago First seen · 157 lines · 56 tokens per session scan A d59bfaf6190d
manager is a skill published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 56 tokens to every session and 10,361 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.