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/zonesgit 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.00460 |
| Opus 5 | $0.00005 | $0.00230 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade C, and why
zones 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 providing a quick overview of Cloudflare zones using the cf CLI.
For action=list (default):
- Run
cf zones list --json - Display results in a readable table showing:
- Zone name (domain)
- Zone ID
- Status (active, pending, etc.)
- Name servers (abbreviated)
- Count total zones and display at the top
For action=get:
- Verify $ARGUMENTS.zone is provided
- Quote the zone value when shelling out. Run:
cf zones get "$ARGUMENTS.zone" --json - Display detailed zone information including:
- Zone name and ID
- Status
- Name servers (full list)
- Plan type
- Created/modified dates
- Any relevant settings or flags
If zone is required but not provided for the get action, prompt the user to provide the zone name.
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 · 46 lines · 11 tokens per session scan C e103302ff4ca
zones 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 460 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.