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 dryvist/claude-code-plugins --skill homelab-runbooksgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/homelab-runbooks)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/homelab-runbooks"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/homelab-runbooks.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.00056 | $0.01249 |
| Opus 5 | $0.00028 | $0.00624 |
| Sonnet 5 | $0.00011 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
homelab-runbooks 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Homelab Operations Runbooks
Generic, vendor/topology-neutral runbooks for recurring homelab operator tasks. Every identifier below is a placeholder — substitute your own node names, domain, and env-var values; never commit real ones.
Operating note: secrets are var-names, never values
Every credential in this skill is referenced by its environment/secret
variable name (e.g. IDRAC_USERNAME, <NODE>_BMC_HOSTNAME), never a
literal value. When writing runbooks, commits, or PRs in a public repo:
reference the variable name that holds a secret, not the secret itself, and
never a real hostname/IP/node name either — use <node> / proxmox-N /
<domain> placeholders. See also: always address a host by its FQDN,
never a hardcoded IP — IPs are derived from a VLAN + host-id scheme and
silently go stale the moment a guest moves.
Runbook 1: Power-managed DR node wake (Dell PowerEdge / iDRAC)
Some DR/standby nodes in a Dell PowerEdge estate sleep nightly to save power
and are woken on demand via their iDRAC BMC (ipmitool), same procedure for
any node in the class:
ipmitool -I lanplus -H <node>-bmc -U "$IDRAC_USERNAME" -E chassis power on
-Ereads the password from theIPMITOOL_PASSWORDenv var — never put the password on the command line or in shell history.IPMITOOL_PASSWORDandIDRAC_USERNAMEare sourced from the secrets engine at runtime; the BMC hostname comes from a per-node var, generalized here as<NODE>_BMC_HOSTNAME.- On the target host, the credential is delivered via a root-only
EnvironmentFile(mode 0600), never inlined in a unit file or script.
Automation pattern (e.g. an idrac_power Ansible role/play): gate the
power-on task on a per-node flag such as pve_power_managed: true, then
ipmitool ... chassis power on followed by wait_for_connection (poll SSH
until the node answers) before running any converge against it.
Gotcha — BMC network isolation. The BMC/OOB network is usually its own
isolated VLAN that the operator's own workstation cannot route to. Delegate
the ipmitool call to a controller host that already has OOB network
reachability (delegate_to: in Ansible) rather than trying to run it from
wherever the operator happens to be.
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.
- 4d ago First seen · 101 lines · 56 tokens per session scan A ab997ff3055c
homelab-runbooks is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,249 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-09-04.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
cloudflare-workers-publish
Deploy static HTML files to Cloudflare Workers with 1Password credential management.
doppler-workflows
Manage credentials and secrets through Doppler for publishing and deployment workflows. Use whenever the user needs to publish Python packages.
infra-deploy
Cal.com self-hosted deployment to GCP Cloud Run with Supabase PostgreSQL. Docker Compose for local dev.