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 skills add osouthgate/agent-plus-skills --skill hcloud-remotegit clone --depth 1 https://github.com/osouthgate/agent-plus-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/skills/osouthgate/agent-plus-skills/hcloud-remote)<a href="https://agentmods.dev/skills/osouthgate/agent-plus-skills/hcloud-remote"><img src="https://agentmods.dev/badge/skills/osouthgate/agent-plus-skills/hcloud-remote.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.00063 | $0.01795 |
| Opus 5 | $0.00032 | $0.00898 |
| Sonnet 5 | $0.00013 | $0.00359 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade B, and why
hcloud-remote scanned grade B with 2 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Or globally in `~/.claude/settings.json`: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
On Windows, piping curl output into `python3 -c "..."` with a multiline string gets mangled by the bash shim (stray `||` parsed as `goto :error`). The previous workaround was writing a temp `.py` file every time. This wr How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hcloud-remote
Stdlib-only Python 3 CLI for the narrow slice of Hetzner Cloud API you actually use when you have one or two VPSes and no Terraform. Lives at ${CLAUDE_SKILL_DIR}/../../bin/hcloud-remote; the plugin auto-adds bin/ to PATH.
When to reach for this
- User needs an IP address or status for a Hetzner server.
- User wants to reboot or snapshot before risky work.
- User wants to SSH in but doesn't have the IP in their head.
Do NOT use for: volumes, networks, firewalls, load balancers, floating IPs, image management, server creation/destruction. If you find yourself wanting any of those, reach for Terraform / hcloud (the upstream CLI) instead — this wrapper intentionally doesn't cover them.
When NOT to use this — fall back to hcloud CLI directly
This wrapper is deliberately tiny. It covers server list/show/reboot, snapshot create/list, and ssh — nothing else. For anything outside that slice, skip hcloud-remote and use the upstream hcloud CLI (or Terraform) directly. It's already authed on the same HCLOUD_TOKEN.
Specific cases where you should use hcloud ... (or Terraform) directly, not hcloud-remote:
- Creating or destroying servers. →
hcloud server create .../hcloud server delete <name>. The wrapper has noserver createorserver deleteon purpose — those are Terraform's job for anything you care about keeping. - Volumes, networks, load balancers, floating IPs, firewalls. →
hcloud volume|network|load-balancer|floating-ip|firewall .... None of these are wrapped; don't try to coerceserver showinto revealing attached-volume details. - SSH key management (adding/listing/rotating project SSH keys). →
hcloud ssh-key .... The wrapper'ssshsubcommand just uses your local~/.ssh/*— it doesn't manage Hetzner's registered keys. - Image management beyond snapshots — deleting snapshots, listing backups/ISOs, rebuilding from an image. →
hcloud image .... The wrapper creates and lists snapshots but never deletes them (safety); prune viahcloud image delete <id>or the Console. - Rescue mode, power on/off, rename, change type, resize. →
hcloud server enable-rescue|poweron|poweroff|rename|change-type .... Onlyrebootis wrapped.
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.
- 7d ago First seen · 127 lines · 63 tokens per session scan B 521dc429d11a
hcloud-remote is a skill published in the GitHub repository osouthgate/agent-plus-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,795 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
coolify
Operate a Coolify self-hosted PaaS through the @masonator/coolify-mcp server. Use this skill whenever the user asks Claude to inspect, deploy, restart, debug, or manage anything on Coolify — including applications, databases, services, servers, projects, environments, deployments, environment variables, private keys…
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
virtualization-operations
Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.