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.
git 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/updatespec)<a href="https://agentmods.dev/commands/naniiluja/ccf/updatespec"><img src="https://agentmods.dev/badge/commands/naniiluja/ccf/updatespec/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/commands/naniiluja/ccf/updatespec"><img src="https://agentmods.dev/badge/commands/naniiluja/ccf/updatespec.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.00077 | $0.04303 |
| Opus 5.5 | $0.00031 | $0.01721 |
| Sonnet 5.5 | $0.00015 | $0.00861 |
| Haiku 4.5 | $0.00008 | $0.00430 |
Grade A, and why
updatespec 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running CCF /ccf:updatespec. Distill this session's lessons into two places — the project spec (.claude/) and Claude Code's system memory — so future sessions start with fresh context and repeat fewer mistakes.
Why two places, and what goes where:
- Spec (
CLAUDE.md+.claude/rules/) is loaded as a user message tagged "may not be relevant", so it carries lower weight. It suits project rules: conventions, architecture, tech stack, tooling.- Memory (
~/.claude/projects/<path>/memory/) is loaded into the system prompt and is not down-weighted, so Claude follows it more strongly. It suits anti-mistake feedback and user preferences across sessions.- No duplication: anything already in
CLAUDE.mdstays there. When a rule inCLAUDE.mdkeeps getting forgotten, write afeedbackmemory that reinforces it and states why, instead of copying its content.
0a. Style for user-facing text (applies to every step below that writes text for the user)
Scope boundary: this rule governs CCF-generated text meant for the human reader (the diff explanation, the "why" line, the plan and task sync notes shown to the user). It does NOT apply to the CCF repo's own source, which stays English per .claude/rules/components.md (never translate the repo itself).
- 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.
- 2d ago Changed 745884545521
- 19d ago Changed · +12 lines · +31 tokens per session 5da9f115a52f
- 20d ago Changed · +15 lines adf7be01f6c7
- 22d ago Changed 42956d547a16
- 1mo ago Changed 74bed75e000e
- 1mo ago First seen · 78 lines · 46 tokens per session scan A f1b90f084bb9
updatespec is a command published in the GitHub repository naniiluja/ccf (9 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 4,303 once invoked, about $0.0003 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 commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
show
Show this project's saved Recall context (.recall/context.md).
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
phase
Orchestrate a full roadmap phase. Designs features, imports to tracker, creates issues, then executes.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.