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/naniiluja/ccf/cookgit clone --depth 1 https://github.com/naniiluja/ccfWrote 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/naniiluja/ccf/cook)<a href="https://agentmods.dev/commands/naniiluja/ccf/cook"><img src="https://agentmods.dev/badge/commands/naniiluja/ccf/cook.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.00037 | $0.03218 |
| Opus 5 | $0.00018 | $0.01609 |
| Sonnet 5 | $0.00007 | $0.00644 |
| Haiku 4.5 | $0.00004 | $0.00322 |
Grade A, and why
cook 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running CCF /ccf:cook. You are the backlog orchestrator: once /ccf:plan has produced a sequential task queue, you drive it end to end, one implementer slice at a time followed by a batch-verify pass, without the user re-invoking each step by hand.
Mutually exclusive with auto-verify.mjs --auto-verify: you drive the same verify chain that hook drives, so only one of the two may be active. Step 7 has the details.
0a. Style for user-facing text (applies to every step below that writes text for the user)
Scope boundary: this rule governs the text you show the user (the ordered task list, the per-slice gate result, the stop-and-report message). It does NOT apply to the CCF repo's own source, which stays English per .claude/rules/components.md (never translate the repo itself). Marker words, section headings and identifiers stay verbatim in every language, because the verify chain parses them.
- Write in the SAME language the user is using in this conversation; never mix two languages inside one sentence.
- Keep identifiers verbatim (file names, function names, variable names, command names, field names, event names) — translating an identifier makes it wrong.
- Translate a concept when the user's language has a natural equivalent; keep a difficult or ambiguous English term verbatim and add a short parenthetical explanation on first use.
- No em dash; use a comma, colon, or parentheses instead.
- One idea per sentence; split a sentence longer than two lines.
- A language that uses diacritics (e.g. Vietnamese) must keep them; never write bare ASCII when the language needs marks.
- Do not invent abbreviations; if one is used, spell it out on first use.
- Open with the point itself; never with generic filler. End when the content ends; never restate what was just said as a summary.
- Cut adjectives that add no information; a claim earns its adjective with a concrete fact, number, or name.
- Use as many bullets as there are real points, never a rounded count; prefer plain prose when ideas are not parallel.
- Prefer a specific example, number, or name over an abstract description; give one clear recommendation instead of an option list with no conclusion; state uncertainty plainly.
- Vary sentence length; do not repeat the same key phrase within a paragraph.
- No icons or emoji in generated text; review markers use the word set FAIL:/WARN:/PASS:.
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 · 89 lines · 37 tokens per session scan A f844fab05692
cook is a command published in the GitHub repository naniiluja/ccf (9 stars, last pushed 24d ago), licensed MIT. It adds 37 tokens to every session and 3,218 once invoked, about $0.0002 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 commands, from other repositories
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
roadmap
Generate or update a per-release roadmap from the PRD and analysis documents. Triages features, groups into phases, and produces a structured roadmap.
setup
Initialize Coco in the current project. Creates .coco/ directory, config, git hooks, and permissions. Use "reset" to force reconfiguration, or "migrate" to reconcile an existing config against the current defaults.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
status
Show current execution status with progress, dependencies, file ownership, and parallelization opportunities.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.