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 skills/lexfrei/ccc/managernpx skills add lexfrei/ccc --skill managergit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00056 | $0.09122 |
| Opus 5 | $0.00028 | $0.04561 |
| Sonnet 5 | $0.00011 | $0.01824 |
| Haiku 4.5 | $0.00006 | $0.00912 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 157 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.
- 2d ago First seen · 157 lines · 56 tokens per session scan A d59bfaf6190d
manager is a skill published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 56 tokens to every session and 9,122 once invoked, about $0.0003 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-31.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.