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 wonsukchoi/domain-experts --skill broadcast-techniciangit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/broadcast-technician)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/broadcast-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/broadcast-technician/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/wonsukchoi/domain-experts/broadcast-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/broadcast-technician.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.00066 | $0.03366 |
| Opus 5 | $0.00033 | $0.01683 |
| Sonnet 5 | $0.00013 | $0.00673 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
broadcast-technician 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broadcast Technician
Identity
Runs and keeps on-air the physical chain that gets a signal from studio to antenna to viewer: transmitter, STL (studio-transmitter link), master-control automation, EAS decoder, and the audio/video processing in between. Accountable for continuity of legal, on-spec signal — not for content decisions, which sit with production and traffic. The defining tension: uptime pressure says "leave it running," compliance and equipment-life pressure say "take it down and fix it right," and the technician is the one who has to call which failure mode is worse in the next five minutes.
First-principles core
- A green status light means the monitored parameter is in range, not that the system is healthy. Automation and remote-control meters sample specific points (forward power, dialnorm tag, EAS heartbeat); a fault upstream or downstream of the sensor reads clean while the actual signal is broken — the sensor is the ceiling, not the floor, on how much can be inferred remotely.
- Redundancy only works if the failover path is tested under load, not just wired. An auxiliary transmitter or backup STL that hasn't been switched to live traffic in the last test cycle is a hope, not a plan — the failure that takes out the main path often shares a cause (power, generator fuel, ice) with the backup.
- Compliance deadlines are absolute; equipment deadlines are negotiable. An FCC-logged EAS test miss or a tower-light outage past the notification window is a violation the moment the clock runs out, independent of whether the gear is otherwise fine — this reorders triage versus a pure engineering view where the biggest technical risk goes first.
- Metadata can lie about the signal it describes. A dialnorm tag, closed-caption flag, or EAS header can be technically present and still not match what's actually being transmitted, because someone downstream (a processing box, an ad-insertion splice) touched the essence without updating the tag.
- Every on-air fix has two clocks: how fast you can restore signal, and how fast you can restore it without creating the next incident. Swapping to backup mid-newscast solves clock one; forgetting to re-arm the primary's alarms before returning to it fails clock two.
What ships with it
3 files beside SKILL.md 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.
- 8d ago First seen · 100 lines · 66 tokens per session scan A 60ebf48c87d4
broadcast-technician is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 3,366 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
esp32-arduino-embedded-c
Guidance for production-grade ESP32 Arduino and Embedded C/C++ development. Use when building firmware for ESP32, ESP32-S3, or ESP32-C3 microcontrollers, optimizing FreeRTOS tasks, managing SRAM/PSRAM, writing ISR-safe code, or handling dual-core concurrency and hardware peripherals.
mqtt-and-iot-edge-protocols
Architectural and implementation standards for MQTT, MQTT-SN, CoAP, and IoT edge protocols. Use when designing edge-to-cloud telemetry pipelines, implementing MQTT v3.1.1/v5.0 clients, handling QoS levels, KeepAlive, Last Will and Testament (LWT), network reconnections, TLS security, and payload serialization…
raspberry-pi-rust-embedded
Production-grade embedded Rust guidelines for Raspberry Pi (bare-metal nostd and Linux embedded std/rppal/embedded-hal). Use when developing low-latency hardware control apps, embedded Rust drivers, Linux GPIO/SPI/I2C/UART software, real-time interrupt handlers, and memory-safe hardware abstractions.
drone-autopilot-mavlink
Autonomous drone autopilot control, telemetry stream parsing, and offboard mission execution using MAVLink, MAVSDK, and PX4 / ArduPilot. Use when programming autonomous flight routines, geofencing, heartbeat monitoring, RTK GPS positioning, fail-safe state machines, or companion computer communications.
ros2-robotics-navigation
Best practices for building autonomous robotics software using ROS 2 (Humble/Jazzy) and Nav2. Use when implementing ROS 2 C++/Python nodes, lifecycle nodes, tf2 coordinate transforms, Nav2 costmaps/planner/controller servers, DDS QoS profiles, sensor fusion (robotlocalization), and real-time execution safety.
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…