Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/technicalpickles/pickled-claude-plugins/cleangit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/clean)<a href="https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/clean"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/clean.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 | $0.00006 | $0.00212 |
| Opus 5 | $0.00003 | $0.00106 |
| Sonnet 5 | $0.00001 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
clean 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 today.
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
Clean
Remove temporary test fixtures created by the self-test command.
What Gets Removed
tmp/bktide- Cloned test fixture from bktide repositorytmp/bktide-no-claude-md- Test fixture without CLAUDE.md
Process
- Check for tmp directory at
${PLUGIN_ROOT}/tmp/ - List contents to show what will be removed
- Remove the entire tmp directory
- Confirm removal
Example Output
Cleaning stay-on-target test fixtures...
Found:
- tmp/bktide (42 MB)
- tmp/bktide-no-claude-md (41 MB)
Removed 83 MB of test fixtures.
Notes
- The tmp directory is gitignored, so these are local-only files
- Re-running self-test will recreate the fixtures as needed
- Safe to run multiple times (no error if tmp doesn't exist)
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.
- today First seen · 39 lines · 6 tokens per session scan A bcded05cffae
clean is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 212 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.