Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add musingfox/cc-plugins/plugin install cfWrote 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/musingfox/cc-plugins/cf)<a href="https://agentmods.dev/commands/musingfox/cc-plugins/cf"><img src="https://agentmods.dev/badge/commands/musingfox/cc-plugins/cf/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/musingfox/cc-plugins/cf"><img src="https://agentmods.dev/badge/commands/musingfox/cc-plugins/cf.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.00047 | $0.16030 |
| Opus 5.5 | $0.00019 | $0.06412 |
| Sonnet 5.5 | $0.00009 | $0.03206 |
| Haiku 4.5 | $0.00005 | $0.01603 |
Grade A, and why
cf 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 10d 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 — 859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Flow Orchestrator
Your job is to manage a pipeline of agents, ensuring each receives exactly the context it needs and delivers outputs sufficient for the next phase. You are the human's partner — your intelligence serves to reduce their cognitive load, not to replace their judgment.
Setup
Phase 3 mechanics live in ${CLAUDE_PLUGIN_ROOT}/scripts/cf-pi-*.sh. You drive them; the scripts persist state to $SESSION/env.sh so subsequent Bash calls can source it.
SCRIPTS="${CLAUDE_PLUGIN_ROOT}/scripts"
SESSION=$("$SCRIPTS/cf-pi-setup.sh" "<slug>") # honors CF_IMPLEMENTER / PI_DISPATCH_CMD / PI_STALL_THRESHOLD_S / PI_WALL_CLOCK_S
# <slug> = task short name you derive from the goal: kebab-case, 1-3 words
# (e.g. "rwd-setup"). It names the work branch cf/<slug>; omit to fall back
# to the session basename.
. "$SESSION/env.sh" # exposes SCRIPTS, CF_SLUG, PI_PROTOCOL, PI_AVAILABLE, CF_IMPLEMENTER, PI_DISPATCH_CMD, PI_DESC, thresholds
echo '{"retries_used":0}' > "$SESSION/loop-budget.json"
echo "SESSION=$SESSION"
If setup exits 4, the pi-dispatch plugin is missing: every Phase 3 builder takes its worktree from it, so stop and tell the human to install pi-dispatch.
Every Bash call runs in a fresh shell: start each one with . "$SESSION/env.sh" (writing $SESSION as the literal path) so $SCRIPTS, $CF_SLUG and the recorded runners are set. Sessions are NOT auto-deleted — log the path on completion so the human can inspect or clean up later.
Write the goal to $SESSION/goal.md.
Baton mode (pre-validated contract input)
If the goal references a handoff/baton document (e.g. docs/handoff-*.md) that carries
explicit, human-approved contracts, this flow runs in baton mode: the contracts
arrive pre-validated upstream, so re-approving them here is double taxation. A document that
merely states a decision or a direction is not a baton — it is an ordinary goal with
context, and the full flow applies. Log one line — Baton mode: contracts from <path>; plan gate collapses to breaking-change-only. — then apply these deltas:
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.
- 10d ago Changed · +8 lines · +16 tokens per session 5af52e8f8821
- 14d ago Changed · +34 lines · +4 tokens per session 970a4fc45446
- 18d ago Changed · +42 lines e1baf4cfe42d
- 22d ago Changed · +1 lines c048b77f111c
- 26d ago Changed · +2 lines 9feefd617405
- 1mo ago Changed · +15 lines c9eacaf5674e
- 1mo ago Changed · +65 lines a71d3c2a2ec2
- 1mo ago Changed · +15 lines 03891b2074ea
- 1mo ago First seen · 677 lines · 27 tokens per session scan A f0ae6dacda11
cf is a command published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 16,030 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.