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 damionrashford/media-os --skill ndi-docsgit clone --depth 1 https://github.com/damionrashford/media-osWrote 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/damionrashford/media-os/ndi-docs)<a href="https://agentmods.dev/skills/damionrashford/media-os/ndi-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/ndi-docs/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/damionrashford/media-os/ndi-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/ndi-docs.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.00200 | $0.02350 |
| Opus 5 | $0.00100 | $0.01175 |
| Sonnet 5 | $0.00040 | $0.00470 |
| Haiku 4.5 | $0.00020 | $0.00235 |
Grade A, and why
ndi-docs 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NDI Docs
Context: $ARGUMENTS
Quick start
- Find an NDI API / feature / spec detail: → Step 2 (
search --query <term>) - Read the full section for a topic: → Step 3 (
section --page <page> --id <anchor>) - Grab a whole doc page: → Step 4 (
fetch --page <name>) - Prime cache for offline use: → Step 5 (
index)
When to use
- User asks "what port does NDI use?" or "what's NDI|HX?" or "does NDI 6 support HDR?"
- Need to verify a wire-protocol detail before recommending config (mDNS 5353, TCP 5960, streams 5961+).
- Need the exact SDK-vs-Advanced-SDK feature matrix (routing, multicast, access-control, compressed passthrough).
- Need the official NDI 6 / HX3 / Agilex 7 feature list before claiming support.
- Need to cite the canonical
docs.ndi.videoURL. - Integrating NDI with OBS → check DistroAV (not "obs-ndi" — that repo was renamed/forked).
Step 1 — Know the page catalog
The script only works against a fixed list of known docs.ndi.video pages plus the DistroAV GitHub README. Get the list:
uv run ${CLAUDE_SKILL_DIR}/scripts/ndidocs.py list-pages
Common picks:
| Question | Page |
|---|---|
| "Which NDI SDK do I need?" | sdk-landing |
| "What changed in NDI 6?" | tech-ndi6 |
| "Release notes / version history" | sdk-release-notes |
| "Which ports does NDI use?" | sdk-port-numbers |
| "Does NDI support HDR? PQ / HLG?" | sdk-hdr |
| "SDK vs Advanced SDK differences" | faq-sdk-vs-advanced |
| "OBS + NDI setup" | distroav |
| "NDI docs root / landing" | docs-root |
Read references/pages.md for the full catalog + use-cases.
Step 2 — Search first
When the user names an NDI feature / port / flag / function, search across all pages:
uv run ${CLAUDE_SKILL_DIR}/scripts/ndidocs.py search --query "multicast" --limit 5
When you know the page, scope it (faster, less noise):
uv run ${CLAUDE_SKILL_DIR}/scripts/ndidocs.py search --query "5960" --page sdk-port-numbers
What ships with it
2 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.
- 12d ago First seen · 198 lines · 200 tokens per session scan A 658060746031
ndi-docs is a skill published in the GitHub repository damionrashford/media-os (19 stars, last pushed 3mo ago), licensed MIT. It adds 200 tokens to every session and 2,350 once invoked, about $0.0010 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 skills, from other repositories
loudcheck
Loudness compliance verdicts against formal published standards — EBU R 128, ATSC A/85, or BS.1770 measure-only. Use it when audio or video has to pass a delivery gate: "is this file broadcast-legal?", "will this mix get rejected?", "how far off target is it and what's the exact fix?", batch-checking a delivery…
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
dev
One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install…
storybook-mcp-integration
Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a…