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 Knuckles-Team/hdhomerun-mcp --skill hdhr-doctorgit clone --depth 1 https://github.com/Knuckles-Team/hdhomerun-mcpWrote 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/knuckles-team/hdhomerun-mcp/hdhr-doctor)<a href="https://agentmods.dev/skills/knuckles-team/hdhomerun-mcp/hdhr-doctor"><img src="https://agentmods.dev/badge/skills/knuckles-team/hdhomerun-mcp/hdhr-doctor/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/knuckles-team/hdhomerun-mcp/hdhr-doctor"><img src="https://agentmods.dev/badge/skills/knuckles-team/hdhomerun-mcp/hdhr-doctor.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.00154 | $0.01370 |
| Opus 5 | $0.00077 | $0.00685 |
| Sonnet 5 | $0.00031 | $0.00274 |
| Haiku 4.5 | $0.00015 | $0.00137 |
Grade A, and why
hdhr-doctor 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 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HDHomeRun Doctor
A single diagnostic sweep over an HDHomeRun deployment, matching this fleet's
"doctor" pattern (e.g. container-manager-mcp's cm_doctor). Every check
reports pass/fail/warn/skip plus an action (a concrete next step) on
anything short of a clean pass.
When to use
- "Live TV isn't working" / "why are recordings missing" style troubleshooting.
- Before wiring a tuner into Jellyfin — confirm the device itself is healthy first.
- Producing a status report on an existing deployment (e.g. for a recurring check).
When NOT to use
- Routine channel scan / lineup / tuning operations — this skill only reads
status, it never scans/tunes except the opt-in
signal_strengthcheck (which briefly retunes and releases a tuner). Usehdhr-http-api-ops/hdhr-tuner-controlfor the operations themselves. - Recording-rule management →
hdhr-dvr-ops.
Prerequisites & environment
Connect via the mcp-client skill against the hdhomerun-mcp MCP server.
| Variable | Required | Notes |
|---|---|---|
HDHOMERUN_URL |
✅ | Device to diagnose |
HDHOMERUN_DEVICE_AUTH |
optional | Enables deeper device_auth cloud validation |
DOCTORTOOL |
optional | Toggle this tool domain (default enabled) |
Tools & actions
| Condensed tool | Actions |
|---|---|
doctor_operations |
run (full suite, recommended), or a single check: device_reachable, firmware_model, tuner_count_vs_jellyfin, signal_strength, device_auth, cache_freshness |
Checks performed by run
- device_reachable —
GET discover.jsonsucceeds. - firmware_model — reports ModelNumber/FirmwareName/FirmwareVersion; warns if either field is missing (very old/legacy firmware).
- tuner_count_vs_jellyfin — compares the device's
TunerCountto a paired JellyfinTunerHostentry matched byDeviceId; skipped (not failed) when nojellyfin_url/jellyfin_api_keyis supplied. - signal_strength — for each requested channel: briefly tunes it, reads
ss/snq/seqvia the control protocol, then releases the tuner; warns onss < 40. Skipped when no channels are requested (it is invasive — it uses a tuner — so it is opt-in). - device_auth — DeviceAuth present in
discover.json; optionally validated live against the cloud recording-rules API. - discovery_cache_freshness — age of
~/.config/agent-utilities/hdhomerun_discovery_cache.json; warns past 24h.
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.
- 12d ago First seen · 108 lines · 154 tokens per session scan A 25a66b0c3f38
hdhr-doctor is a skill published in the GitHub repository Knuckles-Team/hdhomerun-mcp (0 stars, last pushed 15d ago), licensed MIT. It adds 154 tokens to every session and 1,370 once invoked, about $0.0008 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-31.
Other skills, from other repositories
preset-health
Nested swiss-knife reference for saved-preset health checks. Read this when the human asks whether saved presets still work, which preset is expired or misconfigured, why system(action="presets") shows a bad connectivity status, or for a safe procedure to enumerate saved presets, classify each failure (expired key…
meraki-monitoring
Cisco Meraki monitoring and diagnostics (read-only) — device availability, loss and latency history, uplink status, live tool results, configuration change log, API request analytics via Cisco's official Meraki MCP. Use when checking Meraki device health, investigating uplink loss, or reviewing recent configuration…
janitor-device
Diagnose and fix slow Mac or Windows performance. Use this skill whenever the user says their computer, laptop, Mac, MacBook, PC, or Windows machine is slow, sluggish, laggy, freezing, stuttering, overheating, beachballing, hanging, or whenever the fans are spinning loudly. Also trigger when the user asks to "clean…
ha-diagnostics-augment
Enriches an existing Home Assistant Custom Integration's diagnostics beyond the scaffold baseline, conforming to spec/ha/diagnostics. Creates or edits diagnostics.py with asyncgetconfigentrydiagnostics (and optional asyncgetdevicediagnostics) returning structured dicts, and routes every…
env-doctor
A diagnostic tool for checking a development environment, including runtimes, ports, and service health.
hermes-system-monitor
Use when running Hermes system health checks.