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 mediamtx-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/mediamtx-docs)<a href="https://agentmods.dev/skills/damionrashford/media-os/mediamtx-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/mediamtx-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/mediamtx-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/mediamtx-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.00238 | $0.02863 |
| Opus 5 | $0.00119 | $0.01432 |
| Sonnet 5 | $0.00048 | $0.00573 |
| Haiku 4.5 | $0.00024 | $0.00286 |
Grade A, and why
mediamtx-docs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Solution:** `clear-cache` then `index`. The GitHub fallback pages already track `main` — if you want a specific release tag, edit the `github-*` URLs in the script's `PAGES` dict (or fetch directly with `urllib`). How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MediaMTX Docs
Context: $ARGUMENTS
Quick start
- Find a config key / API endpoint / feature: -> Step 2 (
search --query <term>) - Read a how-to in full: -> Step 4 (
fetch --page <publish/X or read/X>) - Read one section: -> Step 3 (
section --page <page> --id <anchor>) - Prime cache for offline: -> Step 5 (
index)
When to use
- User asks "how do I push RTSP to MediaMTX?" or "how do I configure JWT auth?" or "what control-api endpoints exist?"
- Need to verify a MediaMTX config key or CLI flag before recommending it.
- Need the canonical mediamtx.org URL to cite.
- Before wiring up a publisher/reader, confirm the protocol endpoint and default port (RTSP 8554, RTMP 1935, HLS 8888, WebRTC 8889, SRT 8890, API 9997, Metrics 9998, pprof 9999).
- For the running-server wrapper + API calls, see the
mediamtx-serverskill.
Step 1 — Know the page catalog
uv run ${CLAUDE_SKILL_DIR}/scripts/mtxdocs.py list-pages
Top-level families:
| Family | When to pick |
|---|---|
kickoff/* |
Install, upgrade, first-run. |
features/* |
Core concepts (publish, read, record, playback, auth, hooks, metrics). |
features/<proto>-specific-features |
Per-protocol options (rtsp-specific-features, rtmp-specific-features, webrtc-specific-features, srt-specific-features). |
features/configuration + features/control-api + features/logging + features/metrics |
Operational — the knobs you actually turn in production. |
references/configuration-file |
Authoritative list of every YAML option. Start here for config questions. |
references/control-api |
Authoritative list of every /v3/* endpoint. |
publish/<client> |
How to SEND a stream in via ffmpeg / gstreamer / OBS / Python / Go / Unity / etc. |
read/<client> |
How to PLAY a stream out via ffmpeg / gstreamer / VLC / OBS / browsers / etc. |
github-readme, github-mediamtx.yml, github-apidocs |
Raw upstream files — the ground truth when mediamtx.org is behind. |
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.
- 11d ago First seen · 197 lines · 238 tokens per session scan A f2fa686d5bb7
mediamtx-docs is a skill published in the GitHub repository damionrashford/media-os (18 stars, last pushed 3mo ago), licensed MIT. It adds 238 tokens to every session and 2,863 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-design
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
api-design
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs. Use when specifying the wire contract an endpoint exposes, choosing a versioning scheme, or standardizing error response bodies across…
python-backend
Production Python async patterns including asyncio TaskGroup, FastAPI dependency injection and middleware, SQLAlchemy 2.0 async sessions, and database connection pool tuning. Python 3.11+ runtime concerns such as ExceptionGroup, cancellation semantics, and session rollback. Use when building async services, wiring…
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
domain-driven-design
DDD tactical patterns for complex business modeling including entities, value objects, aggregates, domain services, repositories, specifications, and bounded contexts. Python dataclass implementations with TypeScript alternatives. Use when building rich domain models, enforcing invariants, or separating domain logic…
neo4j-getting-started-skill
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building…