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/commands/jmagar/claude-homelab/check)<a href="https://agentmods.dev/commands/jmagar/claude-homelab/check"><img src="https://agentmods.dev/badge/commands/jmagar/claude-homelab/check/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/commands/jmagar/claude-homelab/check"><img src="https://agentmods.dev/badge/commands/jmagar/claude-homelab/check.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.00010 | $0.00102 |
| Opus 5 | $0.00005 | $0.00051 |
| Sonnet 5 | $0.00002 | $0.00020 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
check 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 9d 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
Latest screenshot: !echo "$HOME/Pictures/Screenshots/$(ls -t "$HOME/Pictures/Screenshots/" | head -1)"``
Read and describe the image at that path. If the user provided additional instructions in the command arguments, apply them (e.g. "what's in the top right corner", "extract the text", "what error is shown").
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.
- 9d ago First seen · 9 lines · 10 tokens per session scan A 4414d5803bc4
check is a command published in the GitHub repository jmagar/claude-homelab (78 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 102 once invoked, about $0.0001 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 commands, from other repositories
figma-style
Generate styling code from Figma designs matching the project's design system.
statusline-help
Explain the custom statusline — what every line/field means, data source, colors, and the location knob.
design-implement
Thin entry point for /design-implement [--route ] [--viewport WxH] [--from-screenshots] [--dry-run] — parses and validates the argument shape only, then hands control to the design-implement skill. No run logic lives here.
impact
Cross-repo impact analysis — graph-aware (Graphify) with a live ripgrep fallback.
sweep-stale-flags
Find feature flags, env vars, and config keys referenced in code but absent from env-check / settings — dead toggles that pretend to gate behaviour.
ci-diagnose
Deep-dive diagnostic on a failed GitLab pipeline — fetches failed job traces, pattern-matches common errors, proposes fixes.