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.
git clone --depth 1 https://github.com/ThrownLemon/claude-code-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/thrownlemon/claude-code-plugins/dns)<a href="https://agentmods.dev/commands/thrownlemon/claude-code-plugins/dns"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/dns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/thrownlemon/claude-code-plugins/dns"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/dns.svg" alt="Reviewed on agentmods" width="80" 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.00878 |
| Opus 5.5 | $0.00004 | $0.00351 |
| Sonnet 5.5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade C, and why
dns 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 1mo 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.
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 managing Cloudflare DNS records using the cf CLI. Based on the provided arguments, execute the appropriate command.
Quote every user-supplied value when shelling out (e.g. "$ARGUMENTS.zone"). Unquoted values would let shell metacharacters in zone names, record names, or content execute. This applies to every cf call below.
For action=list:
- If $ARGUMENTS.zone is provided, run
cf dns list "$ARGUMENTS.zone" --json - Display the results in a readable table format
- If no zone provided, first list zones with
cf zones list --jsonand ask which one to query
For action=add:
- Verify required parameters: zone, record-type, name, content
- Build the command (quote every value):
cf dns create "$ARGUMENTS.zone" --type "$ARGUMENTS.record-type" --name "$ARGUMENTS.name" --content "$ARGUMENTS.content" --json - Proxied behavior: the default is
true. If$ARGUMENTS.proxiedis omitted or equals "true", append--proxied. If it explicitly equals "false", omit the flag. - If $ARGUMENTS.ttl is provided, append
--ttl "$ARGUMENTS.ttl" - Display the created record details
For action=delete:
- Verify required parameters: zone, record-id
- ALWAYS confirm with the user before deleting: "Are you sure you want to delete DNS record $ARGUMENTS.record-id from zone $ARGUMENTS.zone? (yes/no)"
- Only proceed if user confirms with "yes" or "y"
- Run
cf dns delete "$ARGUMENTS.zone" "$ARGUMENTS.record-id" --json - Display deletion confirmation
For action=export:
- Verify $ARGUMENTS.zone is provided
- Run
cf dns export "$ARGUMENTS.zone" - Display the bind-format output
If any required parameters are missing for the specified action, prompt the user to provide them.
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.
- 1mo ago First seen · 70 lines · 11 tokens per session scan C f26b6e8fb834
dns is a command published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 878 once invoked, about $0.0000 per session on Opus 5.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
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…