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-statusgit 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-status)<a href="https://agentmods.dev/commands/danjdewhurst/hcloud-skills/hcloud-status"><img src="https://agentmods.dev/badge/commands/danjdewhurst/hcloud-skills/hcloud-status.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.00017 | $0.00259 |
| Opus 5 | $0.00009 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
hcloud-status 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
Show a comprehensive overview of the current Hetzner Cloud infrastructure.
Steps
-
Show the active context:
hcloud context active -
List all resources using individual commands for a clear summary:
hcloud server listhcloud network listhcloud firewall listhcloud volume listhcloud floating-ip listhcloud primary-ip listhcloud load-balancer listhcloud ssh-key listhcloud certificate listhcloud placement-group listhcloud zone listhcloud storage-box list
-
Present a concise summary highlighting:
- Total resource counts per type (skip types with zero resources)
- Servers that are powered off or in error state
- Unattached volumes
- Unassigned floating IPs or primary IPs
- Any resources with protection enabled
- Any notable states or warnings
Run all list commands and present the summary. Skip resource types that return empty results.
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 · 38 lines · 17 tokens per session scan A 964e747e2c19
hcloud-status is a command published in the GitHub repository danjdewhurst/hcloud-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 259 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-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: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-workers:optimize
Analyze and optimize Cloudflare Workers performance. Checks bundle size, caching, memory usage, and provides actionable recommendations.
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.