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 Bitbull-Ideas/hermes.skills --skill hetzner-ansible-labgit clone --depth 1 https://github.com/Bitbull-Ideas/hermes.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/bitbull-ideas/hermes.skills/hetzner-ansible-lab)<a href="https://agentmods.dev/skills/bitbull-ideas/hermes.skills/hetzner-ansible-lab"><img src="https://agentmods.dev/badge/skills/bitbull-ideas/hermes.skills/hetzner-ansible-lab/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/skills/bitbull-ideas/hermes.skills/hetzner-ansible-lab"><img src="https://agentmods.dev/badge/skills/bitbull-ideas/hermes.skills/hetzner-ansible-lab.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.00051 | $0.03329 |
| Opus 5 | $0.00026 | $0.01665 |
| Sonnet 5 | $0.00010 | $0.00666 |
| Haiku 4.5 | $0.00005 | $0.00333 |
Grade A, and why
hetzner-ansible-lab 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 11d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 11d ago First seen · 365 lines · 51 tokens per session scan A 2c48bf1b83a2
hetzner-ansible-lab is a skill published in the GitHub repository Bitbull-Ideas/hermes.skills (2 stars, last pushed 2mo ago), licensed AGPL-3.0. It adds 51 tokens to every session and 3,329 once invoked, about $0.0003 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 skills, from other repositories
lovable
Lovable MCP tool usage — deploy projects, message agent, test with agent-browser. Minimize credits by delegating to local repo.
agent-browser
Browser automation via Chrome/Chromium CDP — open, snapshot, click, screenshot. For testing web apps, mobile layouts, and automated interactions without Playwright/Puppeteer.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
load-test-ops
Trigger, monitor, update, profile, and stop Camunda load tests using gh CLI and kubectl directly — no MCP server required.
deploy-verify
Deploy to staging/preview and prove it works before anything reaches users — runs pre-flight gates (types, tests, env, migrations, build), deploys, smoke-tests the live URL, diagnoses failures, and ends by writing a machine-readable verdict artifact that a release orchestrator can trust. Use for "/deploy-verify"…
qa-release-risk-governance
A release-risk assessment and rollout guide for deciding whether a software change is ready to ship. It also covers gradual releases, monitoring, and rollback plans.