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-reset)<a href="https://agentmods.dev/commands/iliaal/ccc-plugin/ccc-reset"><img src="https://agentmods.dev/badge/commands/iliaal/ccc-plugin/ccc-reset/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-reset"><img src="https://agentmods.dev/badge/commands/iliaal/ccc-plugin/ccc-reset.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.00725 |
| Opus 5.5 | $0.00009 | $0.00290 |
| Sonnet 5.5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
ccc-reset 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reset and rebuild a ccc index
Drops the project's index databases and performs a full re-index from scratch. Use this after:
- Editing
.cocoindex_code/settings.ymlto change includes/excludes - Switching embedding device (CPU ↔ CUDA — embeddings are tied to the device that produced them)
- Index corruption or weird state
- Upgrading
cocoindex-codeto a version with incompatible storage
Do NOT use for routine refresh — that's /ccc-reindex. Reset is destructive and pays the full embedding cost.
Step 1: Resolve the target and confirm
$ARGUMENTS is the project path. If empty, fall back to cwd. Verify it has .cocoindex_code/settings.yml — if not, stop and tell the user to run /ccc-onboard first.
Before touching anything, confirm with the user what's about to happen: "About to reset ccc index for <project>. This drops the existing database and rebuilds from scratch — on CUDA this typically takes 1-10 minutes depending on project size. Proceed?" Wait for explicit yes.
Skip confirmation only if $ARGUMENTS contains --yes.
Step 2: Capture pre-reset state
Run cd <project> && ccc status and record the current chunk count, file count, and language breakdown. This is the baseline for the post-reset diff.
Step 3: Drop the index
cd <project> && ccc reset -f
The -f skips the interactive confirmation inside ccc reset. Report what was deleted (it lists the dropped files).
Step 4: Re-index
cd <project> && ccc index
Almost always takes longer than 30 seconds for a full rebuild. Run in background, stream or poll the output file, and report progress to the user every minute or so if it's taking a while.
Step 5: Verify and report
After ccc index completes:
- Run
cd <project> && ccc statusand compare to the pre-reset baseline. Chunk count should be similar (minor drift is expected from chunker non-determinism). - If the chunk count dropped by more than 20%, that's a red flag — surface it to the user.
- Run one sanity query against the new index to prove it's functional. Pick something obvious from the project context ("authentication", "main entry point", "config", whichever fits).
- Report: elapsed time, old vs. new chunk count, sanity-query top hit and score.
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 · 60 lines · 22 tokens per session scan A d6621e1445a9
ccc-reset 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 725 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).