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/danjdewhurst/hcloud-skills/hcloud-cleanupgit clone --depth 1 https://github.com/danjdewhurst/hcloud-skillsWrote 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/danjdewhurst/hcloud-skills/hcloud-cleanup)<a href="https://agentmods.dev/commands/danjdewhurst/hcloud-skills/hcloud-cleanup"><img src="https://agentmods.dev/badge/commands/danjdewhurst/hcloud-skills/hcloud-cleanup.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.00018 | $0.00400 |
| Opus 5 | $0.00009 | $0.00200 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
hcloud-cleanup 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 5d 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
Scan for unused or orphaned resources and help clean them up.
Steps
-
Show context: Run
hcloud context activeto confirm scope. -
Scan for unused resources by running these commands:
a. Unattached volumes: Run
hcloud volume list -o jsonand filter for volumes where server is null/empty.b. Unassigned floating IPs: Run
hcloud floating-ip list -o jsonand filter for IPs where server is null/empty.c. Unassigned primary IPs: Run
hcloud primary-ip list -o jsonand filter for IPs where assignee is null/empty.d. Powered-off servers: Run
hcloud server list --status offto find servers that may be forgotten.e. Empty networks: Run
hcloud network list -o jsonand filter for networks with no servers attached.f. Unused SSH keys: Run
hcloud ssh-key listand note any that may not be in use (can't be determined automatically, but list them for review).g. Orphaned snapshots: Run
hcloud image list --type snapshotto review old snapshots. -
Present findings: Show a categorized summary of potentially unused resources with their details (name, ID, age, size where applicable).
-
Clean up: For each category with findings, ask if the user wants to delete them. Process deletions one category at a time, confirming before each batch.
-
Summary: Show what was cleaned up and what remains.
Important: Always check for protection before attempting deletion. If a resource has protection enabled, note this and skip it unless the user explicitly asks to remove protection first.
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.
- 5d ago First seen · 35 lines · 18 tokens per session scan A 3d81a7fc016b
hcloud-cleanup is a command published in the GitHub repository danjdewhurst/hcloud-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 400 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
cloudflare-images:validate-config
Validate wrangler.jsonc configuration, verify Cloudflare Images bindings, check environment variables, and test Workers integration. Ensures correct setup for using Cloudflare Images with Cloudflare Workers.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.
cloudflare-images:check
Run comprehensive health check and configuration validation for Cloudflare Images. Tests API connectivity, verifies authentication, checks transformations enabled, lists variants, and shows quota usage.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.