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/thrownlemon/claude-code-plugins/purgegit clone --depth 1 https://github.com/ThrownLemon/claude-code-pluginsWhat 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.00011 | $0.00657 |
| Opus 5 | $0.00005 | $0.00329 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade C, and why
purge scanned grade C with 1 finding 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **Reject dangerous tokens.** If a value contains `$(`, backticks, `;`, `|`, `&`, `>`, `<`, or starts with `-` (could be mistaken for a flag), refuse and ask the user to rephrase. **Double-quoting does NOT block comman What it actually says
Input Safety — apply before any Bash invocation
Treat every $ARGUMENTS.* value as untrusted input. Before passing any value to the Bash tool:
- Reject dangerous tokens. If a value contains
$(, backticks,;,|,&,>,<, or starts with-(could be mistaken for a flag), refuse and ask the user to rephrase. Double-quoting does NOT block command substitution —"$(rm -rf /)"still executes inside double quotes. - Prefer the Bash tool's argv contract over constructed shell strings. When you must use a shell string, single-quote the value and escape embedded single quotes (
'\''), or build the command viaprintf %q. - Any
"$ARGUMENTS.foo"patterns shown below are illustrative. Sanitize the value first; never blindly substitute.
You are purging Cloudflare cache for a zone. This is a destructive operation that will immediately affect users serving content from the edge.
ALWAYS confirm with the user before purging.
Quote every user-supplied value when shelling out. Always wrap $ARGUMENTS.zone and $ARGUMENTS.url in double quotes so shell metacharacters (&, ;, $(), etc.) cannot execute.
First, verify the zone exists by running cf zones get "$ARGUMENTS.zone" --json. If the zone doesn't exist, inform the user.
Then, based on the parameters:
If $ARGUMENTS.url is provided (purge specific URLs):
- Parse the comma-separated URLs
- Display what will be purged: "I will purge cache for these URLs: "
- Ask for confirmation: "Are you sure you want to proceed? (yes/no)"
- Only proceed if user confirms with "yes" or "y"
- Run
cf zones purge "$ARGUMENTS.zone" "$ARGUMENTS.url" --json - Display purged URLs and confirmation
If $ARGUMENTS.url is not provided (purge entire cache):
- Display a strong warning: "⚠️ WARNING: This will purge the ENTIRE cache for zone $ARGUMENTS.zone. All cached content will need to be re-fetched from origin."
- Ask for confirmation: "Type 'yes' to confirm you want to purge the entire cache for $ARGUMENTS.zone:"
- Only proceed if user confirms with exactly "yes"
- Run
cf zones purge "$ARGUMENTS.zone" --json - Display confirmation that entire cache was purged
After successful purge, remind the user: "Cache has been purged. It may take a few moments for changes to propagate across all edge locations."
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.
- yesterday First seen · 49 lines · 11 tokens per session scan C d21219084da0
purge is a command published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 657 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.