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.
git clone --depth 1 https://github.com/jmagar/claude-homelabWrote 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/plugins/jmagar/claude-homelab/claude-homelab)<a href="https://agentmods.dev/plugins/jmagar/claude-homelab/claude-homelab"><img src="https://agentmods.dev/badge/plugins/jmagar/claude-homelab/claude-homelab/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/plugins/jmagar/claude-homelab/claude-homelab"><img src="https://agentmods.dev/badge/plugins/jmagar/claude-homelab/claude-homelab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
homelab-core 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.
What it actually says
{
"name": "homelab-core",
"description": "Core homelab agents, commands, and setup/health skills for self-hosted service management. Includes interactive credential setup wizard and unified service health dashboard.",
"version": "1.4.1",
"author": {
"name": "Jacob Magar",
"email": "[email protected]"
},
"repository": "https://github.com/jmagar/claude-homelab",
"homepage": "https://github.com/jmagar/claude-homelab",
"license": "MIT",
"keywords": [
"homelab",
"agents",
"commands",
"skills",
"orchestration",
"setup",
"health"
]
}
What it installs
The manifest is a name and a version. 18 skills, 5 commands, 1 agent travel with it, and installing the plugin installs all of them — 1,827 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill tautulli A 74 tokens
- Skill notebooklm A 67 tokens
- Skill gh-address-comments A 85 tokens
- Skill plex A 76 tokens
- Skill linkding A 69 tokens
- Skill prowlarr A 68 tokens
- Skill radarr A 77 tokens
- Skill sonarr A 75 tokens
- Skill tailscale A 93 tokens
- Skill homelab-health A 85 tokens
- Skill zfs B 136 tokens
- Skill paperless-ngx B 84 tokens
- Skill radicale B 147 tokens
- Skill bytestash B 76 tokens
- Skill memos B 83 tokens
- Skill qbittorrent B 65 tokens
- Skill sabnzbd B 71 tokens
- Skill homelab-setup D 94 tokens
- Command quick-push A 15 tokens
- Command save-to-md A 9 tokens
- Command validate-plan A 10 tokens
- Command check A 10 tokens
- Command deploy B 14 tokens
- Agent notebooklm-specialist A 244 tokens
What ships with it
2 files beside plugin.json 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.
- 11d ago First seen · 22 lines scan A d602adae8c1e
homelab-core is a plugin published in the GitHub repository jmagar/claude-homelab (78 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
deployment-validation
Pre-deployment checks, configuration validation, and deployment readiness assessment.
azure-sdk-rust
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.
railway
Railway agent skills and hosted MCP server for deploying, configuring, monitoring, and troubleshooting apps and infrastructure on Railway from Claude Code. Manage services, environments, deployments, databases, object storage, networking, and observability.
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded".
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG, App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker size/runtime/keepnames/FinalizationRegistry/connect.
cloudflare-browser-rendering
Cloudflare Browser Rendering with Puppeteer/Playwright. Use for screenshots, PDFs, web scraping, or encountering rendering errors, timeout issues, memory exceeded.