Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jmagar/claude-homelab/plugin install homelab-coreWrote 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/jmagar/claude-homelab/homelab-health)<a href="https://agentmods.dev/skills/jmagar/claude-homelab/homelab-health"><img src="https://agentmods.dev/badge/skills/jmagar/claude-homelab/homelab-health/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/jmagar/claude-homelab/homelab-health"><img src="https://agentmods.dev/badge/skills/jmagar/claude-homelab/homelab-health.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.00085 | $0.00686 |
| Opus 5 | $0.00043 | $0.00343 |
| Sonnet 5 | $0.00017 | $0.00137 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
homelab-health 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 13d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Homelab Service Health Dashboard
Run the health check script and present results as a clean dashboard.
Run the Check
bash ~/claude-homelab/skills/health/scripts/check-health.sh
Or from the plugin cache (when installed via Claude Code):
bash "${CLAUDE_PLUGIN_ROOT}/skills/health/scripts/check-health.sh"
Present the Dashboard
Parse the JSON output and display as a formatted table:
Service Health Dashboard
========================
Category Service Status URL
-------- ------- ------ ---
Media plex ✓ reachable https://plex.example.com:32400
radarr ✓ reachable https://radarr.example.com
sonarr ⚠ unreachable https://sonarr.example.com
overseerr ○ not configured
prowlarr ✓ reachable https://prowlarr.example.com
tautulli ✓ reachable https://tautulli.example.com
Downloads qbittorrent ✓ reachable https://qbit.example.com
sabnzbd ✓ reachable https://sabnzbd.example.com
Infrastructure unraid-server1 ✓ reachable https://unraid1.example.com/graphql
unraid-server2 ○ not configured
unifi ✓ reachable https://unifi.example.com
tailscale ✓ reachable (API)
Utilities gotify ✓ reachable https://gotify.example.com
linkding ✓ reachable https://links.example.com
memos ⚠ unreachable https://memos.example.com
bytestash ○ not configured
paperless ✓ reachable https://paperless.example.com
radicale ✓ reachable https://cal.example.com
Summary: 12 reachable · 1 unreachable · 5 not configured
Status Icons
| Icon | Status | Meaning |
|---|---|---|
| ✓ | reachable | URL responded (any HTTP code except timeout) |
| ⚠ | unreachable | URL configured but timed out or connection refused |
| ○ | not configured | No URL set in ~/.claude-homelab/.env |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 74 lines · 85 tokens per session scan A 993babb24695
homelab-health is a skill published in the GitHub repository jmagar/claude-homelab (78 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 686 once invoked, about $0.0004 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-30.
Other skills, from other repositories
jira-triage
Parse a Jira ticket past access preflight, classify it as a defect or a change, run the mandatory evidence step that class demands (reproduction / baseline + absence proof), and assign exactly one of five verdicts (already-fixed / cannot-reproduce / needs-fix / needs-info / too-large). NOT for posting the verdict back…
graft
Use when you need to locate, understand, or assess the blast radius of code in a repo that has a graft/ index — "where is X handled", "what does this file expose", "who calls this before I rename it", or first-time orientation in an unfamiliar tree. Answers come from the context graph as ranked file:line hits instead…
troubleshooting
Debug a specific failure, investigate an incident, analyze error logs, or diagnose connectivity on the project's platform. NOT for proactive instrumentation (use monitoring/observability) or writing tests (use testing).
observability
Structured logging and OpenTelemetry distributed tracing, incl. log-trace-metric correlation. NOT for metrics/dashboards/alerts (belong to monitoring) and NOT for Helm health probes.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.