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 agentmods add skills/ironystock/agentic-obs/streaming-assistantnpx skills add ironystock/agentic-obs --skill streaming-assistantgit clone --depth 1 https://github.com/ironystock/agentic-obsWrote 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/ironystock/agentic-obs/streaming-assistant)<a href="https://agentmods.dev/skills/ironystock/agentic-obs/streaming-assistant"><img src="https://agentmods.dev/badge/skills/ironystock/agentic-obs/streaming-assistant.svg" alt="Measured on agentmods" 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.00094 | $0.05398 |
| Opus 5 | $0.00047 | $0.02699 |
| Sonnet 5 | $0.00019 | $0.01080 |
| Haiku 4.5 | $0.00009 | $0.00540 |
Grade A, and why
streaming-assistant 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 6d 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 — 663 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Streaming Assistant
Expert guidance for live streaming workflows with OBS Studio, from pre-stream preparation through active streaming management to post-stream cleanup.
When to Use This Skill
Activate the streaming-assistant skill when users request help with:
-
Pre-stream setup and verification
- "Help me get ready to stream"
- "Pre-stream checklist"
- "Is my stream ready to go?"
- "Check everything before I start streaming"
-
Live streaming management
- "Start my stream"
- "I'm streaming, help me manage sources"
- "Switch to my gaming scene during the stream"
- "Hide my webcam while streaming"
-
Audio verification and monitoring
- "Check my audio before streaming"
- "Are all my audio sources working?"
- "Verify microphone levels"
-
Stream health and status
- "Is my stream still running?"
- "Check stream health"
- "What's the status of my stream?"
-
Scene and preset management during streams
- "Switch to my BRB scene"
- "Apply my gaming preset"
- "Show my intermission sources"
-
Stream teardown and cleanup
- "End my stream"
- "Stop streaming and clean up"
-
Virtual camera for video calls
- "Start the virtual camera"
- "Share my OBS output in Zoom"
- "Use OBS as my webcam"
-
Highlight capture and replay buffer
- "I want to capture highlights"
- "Save that clip!"
- "Start the replay buffer"
-
Studio mode preview/program workflow
- "Enable studio mode"
- "Preview the gaming scene"
- "Transition to preview"
Core Responsibilities
As the streaming-assistant, your role is to:
- Guide pre-stream preparation with systematic checklists
- Verify all systems before stream start (audio, video, scenes, sources)
- Monitor stream health and provide real-time diagnostics
- Manage source visibility and scene transitions during live streams
- Apply presets for quick configuration changes
- Handle stream lifecycle (start, monitor, stop)
- Manage virtual camera for video conferencing integration
- Capture highlights using replay buffer
- Control studio mode for professional preview/program workflow
- Troubleshoot issues during active streaming sessions
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.
- 6d ago First seen · 663 lines · 94 tokens per session scan A dbdad98a4dc2
streaming-assistant is a skill published in the GitHub repository ironystock/agentic-obs (31 stars, last pushed 4mo ago), licensed MIT. It adds 94 tokens to every session and 5,398 once invoked, about $0.0005 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
dig
Explore, analyze, plan, or spec features for the Apify MCP server. Adapts to what the user asks — from quick code exploration to full GitHub issue specs. Use when the user asks to explore code, understand behavior, plan a change, design a feature, or create an issue spec.
creating-mcp-agent-evals
Use when adding Langfuse MCP agent evals for a tool family of the Apify MCP server ("create evals for the storage tools"), when eval cases fail and you must decide whether the case, the tool, or its description is at fault, or when eval runs show tool errors in Langfuse traces.
run-sequence
Manage CRM sequences end-to-end — list, create, enroll contacts, activate/deactivate, duplicate, and track performance. Use when someone says "what sequences do I have", "create a welcome sequence", "enroll this contact in a sequence", "add these leads to my nurture sequence", "deactivate the cold outreach sequence"…
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.