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 obs-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/obs-docs)<a href="https://agentmods.dev/skills/damionrashford/media-os/obs-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/obs-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/obs-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/obs-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.00149 | $0.02591 |
| Opus 5 | $0.00075 | $0.01295 |
| Sonnet 5 | $0.00030 | $0.00518 |
| Haiku 4.5 | $0.00015 | $0.00259 |
Grade A, and why
obs-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 10d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OBS Docs
Context: $ARGUMENTS
Quick start
- Find an
obs_function / callback / event: → Step 2 (search --query <term>) - Read the full section for an API: → Step 3 (
section --page <page> --id <anchor>) - Grab a doc page: → Step 4 (
fetch --page <name>) - Prime cache for offline use: → Step 5 (
index)
When to use
- User asks "what does
obs_source_createtake?" or "what's the signature ofobs_hotkey_register_frontend?" - Need to verify an API name exists before recommending it (prevents hallucinated OBS calls).
- Need to look up an obs-websocket Request / Event / OpCode field.
- Before writing an OBS plugin, script, or obs-websocket client: confirm the real API surface.
- Need the canonical URL to cite an OBS doc.
Step 1 — Know the page catalog
Only the pages below are covered. Get the list:
uv run ${CLAUDE_SKILL_DIR}/scripts/obsdocs.py list-pages
Pick the right page for the question:
| Question | Page |
|---|---|
| How does OBS's architecture work? | backend-design |
| Plugin authoring / source / output / encoder / service module | plugins |
| Qt frontend integration (menus, docks) | frontends |
| Graphics API (effects, shaders, textures) | graphics |
| Python/Lua scripting inside OBS | scripting |
Core lifecycle + global funcs (obs_startup, obs_shutdown) |
reference-core |
Module loader / obs_module_* macros |
reference-modules |
obs_source, obs_output, obs_encoder, obs_service, obs_scene, obs_data, obs_hotkey |
reference-core-objects |
bmalloc, bstrdup, dstr, lists, config, threading, darrays |
reference-libobs-util |
signal_handler, calldata, procedural callbacks |
reference-libobs-callback |
gs_* graphics (textures, effects, vertex buffers, shaders) |
reference-libobs-graphics |
obs_source_frame, obs_source_audio, media IO, video frames |
reference-libobs-media-io |
obs_frontend_* (Qt dock, scene switching, recording control, events) |
reference-frontend-api |
| Install OBS on macOS / Windows / Linux | wiki-install |
| Build a plugin from scratch (CMake, GitHub template) | plugintemplate-readme |
| obs-websocket Requests / Events / OpCodes / Identify handshake | obs-websocket-protocol |
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.
- 10d ago First seen · 221 lines · 149 tokens per session scan A 81bee0921ca9
obs-docs is a skill published in the GitHub repository damionrashford/media-os (18 stars, last pushed 3mo ago), licensed MIT. It adds 149 tokens to every session and 2,591 once invoked, about $0.0007 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
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.
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
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…