hdhr-dvr-ops

hdhr-dvr-ops is a skill for Claude Code, Codex from Knuckles-Team/hdhomerun-mcp. It costs 156 tokens per session (1,411 once invoked), scanned A, original, MIT.

A tool for managing HDHomeRun DVR recording rules and recordings. HDHomeRun is a network TV tuner; a record engine is the separate device or software that stores recordings.

In plain words
What is it for?
Use it to add, change, reorder, or delete recording rules; list or delete stored recordings; refresh recording tasks; or create buffered live-TV links.
Why use it?
It separates cloud recording-rule management from local recording tasks, making it clearer which system must be checked or changed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add, change, reorder, or delete recording rules; list or delete stored recordings; refresh recording tasks; or create buffered live-TV links.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops
Install

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.

Any agent
npx skills add Knuckles-Team/hdhomerun-mcp --skill hdhr-dvr-ops
Clone the repo
git clone --depth 1 https://github.com/Knuckles-Team/hdhomerun-mcp

Made for: Claude Code, Codex.

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 hdhr-dvr-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops/github.svg)](https://agentmods.dev/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops)
Your own site
<a href="https://agentmods.dev/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops"><img src="https://agentmods.dev/badge/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops/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 hdhr-dvr-ops

Your own site · 80×15
<a href="https://agentmods.dev/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops"><img src="https://agentmods.dev/badge/skills/knuckles-team/hdhomerun-mcp/hdhr-dvr-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00156 $0.01411
Opus 5 $0.00078 $0.00705
Sonnet 5 $0.00031 $0.00282
Haiku 4.5 $0.00016 $0.00141

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

Security

Grade A, and why

hdhr-dvr-ops 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.

hdhomerun_mcp/skills/hdhr-dvr-ops/SKILL.md · 111 lines

How it starts

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

HDHomeRun DVR Operations

Two distinct DVR surfaces per https://info.hdhomerun.com/info/dvr_api: SiliconDust's cloud recording-rules API, and the local record-engine API (a separate box/software from the tuner — HDHomeRun SCRIBE, SERVIO, or desktop/NAS record-engine software).

When to use

  • Add/change/reprioritize/delete a recording rule (Series, Movie, or a one-off DateTimeOnly-ChannelOnly rule).
  • List or delete recordings from a record engine's recorded_files.json.
  • Poke the record engine after a rule change so it recomputes tasks.
  • Build a buffered Live TV URL against the record engine.

When NOT to use

  • The household has tuner-only hardware with no DVR/record-engine present — the cloud recording-rules calls will still work (cloud-side), but record_engine_status/recorded_files/poke/delete_recording/ live_tv_url all require a local record-engine BaseURL, which won't exist. Confirm a record engine is on the network first (its own discover.json, distinct from a tuner's).
  • Direct channel lineup / tuner scan → hdhr-http-api-ops.
  • Per-tuner signal/status → hdhr-tuner-control.

Prerequisites & environment

Connect via the mcp-client skill against the hdhomerun-mcp MCP server.

Variable Required Notes
HDHOMERUN_DEVICE_AUTH ✅ (rule actions) Concatenation of every household tuner's DeviceAuth (from each tuner's discover.json)
DVRTOOL optional Toggle this tool domain (default enabled)

Tools & actions

Condensed tool Actions
dvr_operations list_rules, add_series_rule, add_datetime_rule, change_rule, delete_rule, record_engine_status, recorded_files, poke, delete_recording, live_tv_url

Key parameters

  • Rule actions share device_auth (optional — defaults to the client's configured HDHOMERUN_DEVICE_AUTH), series_id/recording_rule_id, channel_only, team_only, recent_only, after_original_airdate_only, start_padding/end_padding (seconds), and date_time_only (unixtime) for one-off rules.
  • record_engine_status/poke take {"storage_engine_base_url"}.
  • recorded_files takes {"storage_url"} (from record_engine_status's StorageURL field).
  • delete_recording takes {"cmd_url", "rerecord"?}cmd_url comes from the recording's own entry in recorded_files, must be POSTed (GET is rejected with 400).
  • live_tv_url takes {"storage_engine_base_url", "channel", "client_id", "session_id"}client_id stable per app instance, session_id unique per new channel request.

Read the full file on GitHub · 111 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. 11d ago First seen · 111 lines · 156 tokens per session scan A deafa6ebd127

Subscribe to this mod's changes

hdhr-dvr-ops is a skill published in the GitHub repository Knuckles-Team/hdhomerun-mcp (0 stars, last pushed 14d ago), licensed MIT. It adds 156 tokens to every session and 1,411 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.

Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens