agentmods.dev

studio-mode-operator

studio-mode-operator is a skill for Claude Code, Codex from ironystock/agentic-obs. It costs 109 tokens per session (2,141 once invoked), scanned A, original, MIT.

A guide for operating OBS Studio's Studio Mode, which lets a broadcaster prepare one scene privately while another scene is live. It covers previewing, rehearsing, switching, and troubleshooting transitions.

In plain words
What is it for?
Use it to stage scenes, preview or rehearse transitions, cut or fade to the next scene, change transition settings, and diagnose preview or transition problems.
Why use it?
It helps prevent unfinished scene changes from appearing on the live broadcast and provides clear steps for changing what viewers see.

Skill for Claude CodeCodex

not rated 31 +2 4mo ago A scan 109 tokens original MIT
View the source file ironystock/agentic-obs
Install

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.

agentmods
npx agentmods add skills/ironystock/agentic-obs/studio-mode-operator
Any agent
npx skills add ironystock/agentic-obs --skill studio-mode-operator
Clone the repo
git clone --depth 1 https://github.com/ironystock/agentic-obs

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for studio-mode-operator

README.md
[![agentmods](https://agentmods.dev/badge/skills/ironystock/agentic-obs/studio-mode-operator.svg)](https://agentmods.dev/skills/ironystock/agentic-obs/studio-mode-operator)
Your own site
<a href="https://agentmods.dev/skills/ironystock/agentic-obs/studio-mode-operator"><img src="https://agentmods.dev/badge/skills/ironystock/agentic-obs/studio-mode-operator.svg" alt="Measured on agentmods" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,141 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00109 $0.02141
Opus 5 $0.00055 $0.01071
Sonnet 5 $0.00022 $0.00428
Haiku 4.5 $0.00011 $0.00214

Measured 5d ago against content hash c730afe1ebec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

studio-mode-operator 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 5d 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.

skills/studio-mode-operator/SKILL.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Studio Mode Operator

Expert guidance for OBS Studio Mode, the two-scene preview/program workflow used by broadcast operators to stage changes before putting them on air.

When to Use This Skill

Activate studio-mode-operator when users request help with:

  • Entering and exiting studio mode

    • "Enable studio mode"
    • "Turn on preview/program"
    • "I want to rehearse transitions"
    • "Disable studio mode, I'm done directing"

  • Preview-side staging

    • "What's on preview right now?"
    • "Queue up the Gaming scene on preview"
    • "Preview the BRB scene without switching"

  • Transitions between preview and program

    • "Cut to preview" (immediate)
    • "Fade to preview over 500ms"
    • "What transition is active?"
    • "Change my default transition to Slide"

  • Transition rehearsal

    • "Show me how the transition will look before I fire it"
    • "Practice the segment change"

  • Troubleshooting studio mode

    • "The transition button isn't doing anything"
    • "My preview scene reverted"

Prefer streaming-assistant for end-to-end stream sessions that only incidentally touch studio mode; reach for this skill when the user's primary focus is the preview/program discipline itself.

Core Responsibilities

  1. Enforce the two-scene mental model — always name both program (live) and preview (staging) when reporting state.
  2. Never clobber program without asking. In studio mode, a scene switch via set_scene bypasses the preview and goes straight to air, which is almost always the wrong thing. Route through preview + transition instead.
  3. Choose the right transition — hard cut for reactive news-style flow, fade for emotional beats, slide/wipe for segment boundaries.
  4. Reconnect state on ambiguity — studio mode can be toggled from the OBS UI without our tools knowing; always verify with get_studio_mode_enabled at the start of a session.

Available Tools

Studio Mode Control

  • get_studio_mode_enabled - Check whether studio mode is active
  • toggle_studio_mode - Enable/disable studio mode

Read the full file on GitHub · 240 lines

Changes

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.

  1. 5d ago First seen · 240 lines · 109 tokens per session scan A c730afe1ebec

Subscribe to this mod's changes

studio-mode-operator is a skill published in the GitHub repository ironystock/agentic-obs (31 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 2,141 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.

Creative and mediaagenticagentsmcpmcp-serverobs
Related

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.

apify/apify-mcp-server · 64 tokens

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.

apify/apify-mcp-server · 71 tokens

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"…

mondaycom/mcp · 133 tokens

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).

sammcj/agentic-coding · 74 tokens

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.

strands-agents/samples · 38 tokens

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.

sammcj/agentic-coding · 57 tokens