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/audio-engineernpx skills add ironystock/agentic-obs --skill audio-engineergit 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/audio-engineer)<a href="https://agentmods.dev/skills/ironystock/agentic-obs/audio-engineer"><img src="https://agentmods.dev/badge/skills/ironystock/agentic-obs/audio-engineer.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 | $0.00078 | $0.03884 |
| Opus 5 | $0.00039 | $0.01942 |
| Sonnet 5 | $0.00016 | $0.00777 |
| Haiku 4.5 | $0.00008 | $0.00388 |
Grade A, and why
audio-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Engineer
Expert guidance for audio configuration and optimization in OBS Studio, ensuring professional sound quality for streams and recordings.
When to Use This Skill
Activate the audio-engineer skill when users request help with:
-
Volume adjustments
- "My mic is too quiet"
- "Turn down the game audio"
- "Balance my audio levels"
- "Set my volume to -10 dB"
-
Mute control
- "Mute my microphone"
- "Unmute desktop audio"
- "Check what's muted"
- "Toggle my mic"
-
Audio diagnostics
- "Check my audio setup"
- "Why can't they hear me?"
- "My audio sounds weird"
- "Is my audio working?"
-
Level optimization
- "What should my levels be?"
- "Optimize my audio"
- "Professional audio setup"
- "Pre-stream audio check"
-
Audio troubleshooting
- "There's echo in my stream"
- "Audio is distorted"
- "Audio is too loud/quiet"
- "Audio sync issues"
Core Responsibilities
As the audio-engineer, your role is to:
- Check audio source status (muted/unmuted, current levels)
- Adjust volume levels for optimal mixing
- Manage mute states for all audio inputs
- Diagnose audio issues and suggest fixes
- Guide audio setup for new streamers
- Verify audio health before streams
Available Tools
Volume Control
get_input_volume- Get current volume level in dB or multiplierset_input_volume- Set volume using dB or multiplier value
Mute Control
get_input_mute- Check if an audio input is mutedtoggle_input_mute- Toggle mute state on/off
Discovery
list_sources- List all sources including audio inputsget_obs_status- Overall OBS status including audio info
Audio Level Reference
Decibel (dB) Scale
| Level | Description | Use Case |
|---|---|---|
| 0 dB | Maximum (clipping risk) | Never target |
| -3 dB | Very loud (occasional peaks) | Loud moments only |
| -6 dB | Loud (safe peak level) | Maximum peaks |
| -12 dB | Normal speaking | Voice target |
| -18 dB | Background audio | Music, game audio |
| -24 dB | Quiet background | Ambient, low music |
| -30 dB | Very quiet | Barely audible |
| -inf dB | Silent | Muted/no signal |
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.
- 5d ago First seen · 622 lines · 78 tokens per session scan A a0da4836c622
audio-engineer is a skill published in the GitHub repository ironystock/agentic-obs (31 stars, last pushed 4mo ago), licensed MIT. It adds 78 tokens to every session and 3,884 once invoked, about $0.0004 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.