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 iliaal/ccc-plugin/plugin install ccc-toolsWrote 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/iliaal/ccc-plugin/ccc-bench)<a href="https://agentmods.dev/commands/iliaal/ccc-plugin/ccc-bench"><img src="https://agentmods.dev/badge/commands/iliaal/ccc-plugin/ccc-bench/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/iliaal/ccc-plugin/ccc-bench"><img src="https://agentmods.dev/badge/commands/iliaal/ccc-plugin/ccc-bench.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.00022 | $0.00922 |
| Opus 5.5 | $0.00009 | $0.00369 |
| Sonnet 5.5 | $0.00004 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
ccc-bench 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run ccc retrieval regression check
Wraps ${CLAUDE_PLUGIN_ROOT}/bin/ccc-bench, which runs the benchmark runner against every *-eval.yaml corpus in the corpus directory, saves timestamped scorecards to history/, and prints a compact aggregates table.
Corpus directory resolution (first match wins):
--corpus-dir DIRargument$CCC_BENCH_CORPUS_DIRenvironment variable$HOME/ai/retrieval-bench(fallback default)
Step 1: Run the benchmark
${CLAUDE_PLUGIN_ROOT}/bin/ccc-bench $ARGUMENTS
Indexing is expected to be warm (no re-index happens here — this only runs ccc search). Each corpus takes 10-60 seconds depending on case count. For a typical 2-corpus setup, total runtime is 1-3 minutes.
If the command runs for more than ~2 minutes, run it with run_in_background: true and poll the output file.
Step 2: Report the summary
Parse the summary table the script prints and surface the key aggregates for each corpus:
- Cases count
- Miss rate (% of queries where no ground-truth file landed in top-10)
- Median first-hit rank (1 is ideal — target file came back as the top result)
- Mean recall@5 and recall@10
Flag anything that looks off — the target thresholds are miss rate ≤ 10%, median first-hit ≤ 3, recall@10 ≥ 0.70. Below those, the corpus either has stale ground truth, or something in the retrieval stack actually regressed.
Step 3: Handle corpus drift gracefully
If the script reports CORPUS DRIFT for any corpus, it means expected_files in the YAML reference files that no longer exist in the project (renamed, deleted, or moved upstream). This is not a retrieval regression — it's the benchmark corpus going stale.
Read the scorecard file (the script prints the path) to see which ground-truth files are missing. Present the list to the user and offer to:
- Update the eval YAML to remove or replace the stale references
- Skip that corpus with
--no-drift-checkfor this run only (fast mode, distorted numbers) - Leave it alone — the drift check is doing its job by flagging it
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.
- 1mo ago First seen · 71 lines · 22 tokens per session scan A 0ea259179900
ccc-bench is a command published in the GitHub repository iliaal/ccc-plugin (1 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 922 once invoked, about $0.0001 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
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
sm-swab
Run slop-mop's iterative development loop for this repository.
release
Generate changelog, bump version, and create git tag.
review
Heavy multi-agent editorial review (4 specialist auditors in parallel).