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 LovelaceLoom/grok-plugin-cc/plugin install grokWrote 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/lovelaceloom/grok-plugin-cc/purge)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/purge"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/purge.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.1 | $0.00011 | $0.00159 |
| Opus 5 | $0.00005 | $0.00079 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
purge 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 8d 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.
What it actually says
!node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" purge "$ARGUMENTS"
This is a destructive operation. It deletes:
- Job metadata JSON files under
${CLAUDE_PLUGIN_DATA}/state/<workspace>/jobs/ - The on-disk stdout/stderr logs for those jobs
It does NOT delete still-running jobs.
Without --older-than, all non-running job records are purged. Use --older-than 30d (or 12h, 45m, 60s) to keep recent jobs.
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.
- 8d ago First seen · 17 lines · 11 tokens per session scan A 722f590e6e2b
purge is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 159 once invoked, about $0.0001 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
plan
Project spec (no args) or feature FRD (with args).
debug
Structured debugging with parallel investigation agents.
review
Multi-agent code review with parallel validation.
gemini-brainstorm-on
Re-enable Gemini grounding on every prompt (it is on by default; this only matters if you previously turned it off).
gemini-challenge
Get Gemini to argue against a decision or propose alternatives.
gemini-research
Research a topic using Gemini's search-grounded or deep research capabilities.