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/gemini-plugin-cc/plugin install geminiWrote 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/gemini-plugin-cc/purge)<a href="https://agentmods.dev/commands/lovelaceloom/gemini-plugin-cc/purge"><img src="https://agentmods.dev/badge/commands/lovelaceloom/gemini-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.00021 | $0.00219 |
| Opus 5 | $0.00010 | $0.00110 |
| Sonnet 5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 6d 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
Forward to the companion's purge subcommand. By default purges every
non-running job; with --older-than <duration>, only purges jobs whose
ended (or started) timestamp is older than that.
Raw user input:
$ARGUMENTS
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" purge "$ARGUMENTS"
Output rules:
- Return the companion's stdout verbatim (it prints how many jobs were purged).
- The plugin never deletes job files for still-running jobs — losing the PID metadata would orphan the process.
- This deletes locally-stored prompts and Gemini outputs. Use it when those may contain sensitive material that should not linger on disk.
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.
- 6d ago First seen · 27 lines · 21 tokens per session scan A 5166a405f12e
purge is a command published in the GitHub repository LovelaceLoom/gemini-plugin-cc (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 219 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
pin
Break checkpoint — status display, session log, optional MEMORY.md update.
wrap
Use when the user wants to wrap up or end the session — "wrap", "I'm done", "close out", "end of session". Runs session log, git check, plan cleanup, backlog review, and done marker.
atlas
Cross-project atlas with an adaptive render — ≤4 projects in scope get detail cards, more get one aligned digest line each, grouped by domain. Facets projects · sessions · memory · plans · specs · plugins · claude.md; a bare run renders all of them except plugins (opt-in, machine-global). --dir NAME|PATH anchors the…
consolidate-tasks
Consolidate all work items from this repo (or all repos with --discover) into TaskWarrior — section-aware scanning, sub-slug routing, dedup, bulk task creation, tombstoning.
overview
PM-style project overview — current state, recent work, backlog priorities, active plans, and sequencing recommendation. Project-scoped: reads from the current repo. Use at the start of a session or when deciding what to work on next.
search-sessions
Search session history by keyword — returns matching sessions with title and prompts.