hcloud-deploy

hcloud-deploy is a command for coding agents from danjdewhurst/hcloud-skills. It costs 15 tokens per session (378 once invoked), scanned A, original, MIT.

An interactive guide for deploying a new server on Hetzner Cloud, a cloud hosting provider.

In plain words
What is it for?
Use it to choose a server type, image, location, SSH key, network, or firewall, then deploy the server.
Why use it?
It helps turn requirements such as purpose, operating system, performance, location, and access needs into a server deployment command.

Command

Part of the hcloud plugin — 7 skills, 3 commands, 1 hook shipped together

Install

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.

agentmods
npx agentmods add commands/danjdewhurst/hcloud-skills/hcloud-deploy
Clone the repo
git clone --depth 1 https://github.com/danjdewhurst/hcloud-skills

Or install hcloud, the plugin that ships this one along with the rest of its 7 skills, 3 commands, 1 hook.

Wrote 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.

agentmods badge for hcloud-deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/danjdewhurst/hcloud-skills/hcloud-deploy.svg)](https://agentmods.dev/commands/danjdewhurst/hcloud-skills/hcloud-deploy)
Your own site
<a href="https://agentmods.dev/commands/danjdewhurst/hcloud-skills/hcloud-deploy"><img src="https://agentmods.dev/badge/commands/danjdewhurst/hcloud-skills/hcloud-deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 378 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00378
Opus 5 $0.00008 $0.00189
Sonnet 5 $0.00003 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 3d ago against content hash d3d58449dd46, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hcloud-deploy 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 3d 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.

commands/hcloud-deploy.md · 36 lines

What it actually says

Guide the user through deploying a new server on Hetzner Cloud.

Steps

  1. Verify context: Run hcloud context active to confirm which project we're deploying to. If no context is active, help the user set one up.

  2. Gather requirements: Ask the user what they need:

    • What is this server for? (web server, database, development, etc.)
    • Any specific OS preference?
    • Any size/performance requirements?
  3. Select server type: Run hcloud server-type list and recommend an appropriate type based on requirements. Show relevant options with pricing context from the type description.

  4. Select image: Run hcloud image list --type system (and --type app if relevant) and recommend an appropriate image.

  5. Select location: Run hcloud location list and let the user choose or recommend based on their region.

  6. SSH key: Run hcloud ssh-key list to check existing keys. If none exist, help create one with hcloud ssh-key create.

  7. Networking (optional): Ask if they need the server attached to a network or firewall. If yes, list available networks/firewalls.

  8. Deploy: Construct and run the hcloud server create command with all selected options. Include --ssh-key for secure access.

  9. Verify: Run hcloud server describe <server> to confirm deployment. Show the server IP and SSH connection command.

  10. Post-deploy (optional): Ask if they want to:

    • Enable backups
    • Enable protection
    • Add labels
    • SSH into the server
Changes

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.

  1. 3d ago First seen · 36 lines · 15 tokens per session scan A d3d58449dd46

Subscribe to this mod's changes

hcloud-deploy is a command published in the GitHub repository danjdewhurst/hcloud-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 378 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.