agentmods.dev

homelab-setup

homelab-setup is a skill for Claude Code from jmagar/claude-homelab. It costs 94 tokens per session (1,569 once invoked), scanned D, original, MIT.

An interactive wizard for setting up the login details and API keys used by claude-homelab service add-ons.

In plain words
What is it for?
Use it after installing the homelab system or when adding services such as Plex, qBittorrent, SABnzbd, Linkding, Unraid, UniFi, Tailscale, or Gotify.
Why use it?
It reduces the work of configuring several services and keeps their credentials in one shared environment file.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT variable. Also seen: reads .claude/ paths.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the homelab-core plugin — 18 skills, 5 commands, 1 agent shipped together

not rated 78repo +3 1mo ago D scan 94 tokens original MIT

Good fit Use it after installing the homelab system or when adding services such as Plex, qBittorrent, SABnzbd, Linkding, Unraid, UniFi, Tailscale, or Gotify.

Compare 6 skills from other repositories ↓
View source ↗ jmagar/claude-homelab
Install

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.

Claude Code
/plugin marketplace add jmagar/claude-homelab
Claude Code
/plugin install homelab-core

Made for: Claude Code.

Or install homelab-core, the plugin that ships this one along with the rest of its 18 skills, 5 commands, 1 agent.

Wrote 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.

agentmods badge for homelab-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmagar/claude-homelab/homelab-setup/github.svg)](https://agentmods.dev/skills/jmagar/claude-homelab/homelab-setup)
Your own site
<a href="https://agentmods.dev/skills/jmagar/claude-homelab/homelab-setup"><img src="https://agentmods.dev/badge/skills/jmagar/claude-homelab/homelab-setup/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.

agentmods 80×15 button for homelab-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/jmagar/claude-homelab/homelab-setup"><img src="https://agentmods.dev/badge/skills/jmagar/claude-homelab/homelab-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,569 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00094 $0.01569
Opus 5 $0.00047 $0.00785
Sonnet 5 $0.00019 $0.00314
Haiku 4.5 $0.00009 $0.00157

Measured 12d ago against content hash 96b9bea6e5a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade D, and why

homelab-setup scanned grade D 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 12d 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

### Step 2: For each selected service, collect credentials

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

Always ensure `chmod 600 ~/.claude-homelab/.env` after writing.
skills/homelab-setup/SKILL.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Homelab Credential Setup Wizard

You are guiding the user through configuring their ~/.claude-homelab/.env file. This is the single credential store for all homelab service plugins.

Before You Start

Check the current state:

[ -f ~/.claude-homelab/.env ] && echo "EXISTS" || echo "MISSING"
[ -s ~/.claude-homelab/.env ] && echo "NON-EMPTY" || echo "EMPTY"

If the file is missing entirely, run setup-creds.sh first to create it from the template:

"${CLAUDE_PLUGIN_ROOT:-$HOME/claude-homelab}/scripts/setup-creds.sh"

The Wizard Flow

Step 1: Ask which services the user runs

Group the choices to make it manageable:

"Which of these do you use? (say all that apply, or 'all', or list numbers)"

Media

  1. Plex — media server
  2. Radarr — movies
  3. Sonarr — TV shows
  4. Overseerr — media requests
  5. Prowlarr — indexers
  6. Tautulli — Plex analytics

Downloads 7. qBittorrent — torrents 8. SABnzbd — Usenet

Infrastructure 9. Unraid — NAS/hypervisor (can have 2 servers) 10. UniFi — network 11. Tailscale — VPN mesh 12. ZFS — storage (no credentials needed, just CLI access)

Utilities 13. Gotify — push notifications 14. Linkding — bookmarks 15. Memos — notes 16. ByteStash — code snippets 17. Paperless-ngx — documents 18. Radicale — calendar/contacts

Wait for the user's response before continuing.

Step 2: For each selected service, collect credentials

Work through services one at a time. For each service:

  1. Tell the user what you need and where to find it
  2. Ask them to paste/type the value
  3. Write it to ~/.claude-homelab/.env immediately using sed -i
  4. Confirm it was saved before moving to the next service

Never echo or log credential values. Use this pattern to write without revealing:

sed -i "s|^SERVICE_URL=.*|SERVICE_URL=$value|" ~/.claude-homelab/.env

If a key doesn't exist in the file yet, append it:

echo "SERVICE_KEY=$value" >> ~/.claude-homelab/.env

Read the full file on GitHub · 157 lines

Changes

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.

  1. 12d ago First seen · 157 lines · 94 tokens per session scan D 96b9bea6e5a7

Subscribe to this mod's changes

homelab-setup is a skill published in the GitHub repository jmagar/claude-homelab (78 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,569 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it D with 2 findings (harvests environment variables, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Codeagentsaiclaude-code-pluginscodexextension
Related

Other skills, from other repositories

mission-creation

Use this skill to create and drive a UAV mission end-to-end through the web UI with the Playwright MCP browser tools on LOCALDEV (https:// ) — rebuild/redeploy, Keycloak login, the multi-step BYROUTE/REALTIME mission wizard, pre-flight, the Start-Mission FSM, AND the full per-drone flight-command lifecycle (arm →…

atretyak1985/swarmery · 176 tokens

github-actions-cicd

Design, review, or debug GitHub Actions workflows — CI jobs (type-check, lint, test, build, security, summary), AWS ECR/ECS deploys, and a standardized per-repo workflow set. NOT for cloud-auth role/OIDC trust details (use aws-cicd-auth) or Dockerfile/image-build mechanics (use docker-build).

atretyak1985/swarmery · 78 tokens

jira-delivery

Close the needs-fix branch for both ticket classes: isolated git worktree, a red test BEFORE any implementation on change tickets, delegation to a core executor, every publish action (push / PR / comment / QA transition) gated behind a green @verification-agent verdict, commit + push + PR, then writeback via…

atretyak1985/swarmery · 114 tokens

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…

atretyak1985/swarmery · 95 tokens

aws-cicd-auth

Configure and review AWS auth for GitHub Actions CI/CD — OIDC role assumption, ECR push perms, ECS deploy perms, least-privilege IAM. Not for application IAM/Cognito, not for GCP.

atretyak1985/swarmery · 50 tokens

deployment

Use this skill for a Helm-upgrade deploy of an app service (the web portal or the edge service) to an EXISTING Kubernetes cluster, plus post-deploy verification. NOT for cluster-level ops -- Minikube/k3s lifecycle, GCP firewall, tunnels, bootstrap secrets (use kubernetes-deployment); NOT for cross-environment…

atretyak1985/swarmery · 79 tokens