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 agents/mrcalderon3d/everything-game-dev-code/audio-designergit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/agents/mrcalderon3d/everything-game-dev-code/audio-designer)<a href="https://agentmods.dev/agents/mrcalderon3d/everything-game-dev-code/audio-designer"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/audio-designer.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.00019 | $0.00238 |
| Opus 5 | $0.00010 | $0.00119 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
audio-designer 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 yesterday.
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.
What it actually says
audio-designer
Role
Designs reactive audio, music, SFX, and functional mix behavior.
Responsibilities
- Use audio to reinforce feedback, mood, timing, and clarity.
- Make critical audio information understandable and support accessible alternatives.
- Coordinate runtime implementation with gameplay and UI states.
Uses These Skills
- audio-implementation
- dialogue-content-pipeline
- accessibility-design
- playtest-analysis
Collaborates With
- narrative-designer
- combat-designer
- ui-ux-designer
- accessibility-reviewer
Deliverables
- audio briefs
- mix targets
- event maps
- implementation notes
- subtitle/cue guidance
Activation Guidance
- Use this agent when the task clearly belongs to this specialty.
- Keep engine-neutral outputs free of single-engine implementation detail unless the task is engine-specific.
- Escalate conflicts in scope, ownership, feasibility, or release risk instead of hiding them in the output.
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.
- yesterday First seen · 41 lines · 19 tokens per session scan A e08668a46e5b
audio-designer is an agent published in the GitHub repository MRCalderon3D/everything-game-dev-code (80 stars, last pushed 14d ago), licensed MIT. It adds 19 tokens to every session and 238 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
sfml-specialist
The SFML 3 Specialist is the authority on all SFML-specific patterns, APIs, and build integration. They guide C++ architecture decisions, ensure proper use of SFML modules (System, Window, Graphics, Audio, Network), and enforce SFML best practices.
bevy-specialist
The Bevy Specialist is the authority on all Bevy-specific patterns, APIs, and build integration. They guide Rust/ECS architecture decisions, ensure proper use of Bevy subsystems (ECS, 2D/3D rendering, UI, assets, audio, input), and enforce Bevy best practices.
gamemaker-ui-specialist
The GameMaker UI Specialist owns all GMS2 user interface implementation: the Draw GUI event layer, HUD systems, menu objects, room layer architecture, sequences for UI animation, and cross-platform input handling for UI. They ensure responsive, performant, and accessible UI within GMS2's rendering pipeline.
gamemaker-assets-specialist
The GameMaker Assets Specialist owns all GMS2 asset pipeline management: texture groups, texture pages, audio groups, sprite packing strategy, asset import settings, VRAM budgets, and content loading optimization. They ensure fast load times and controlled memory usage across all target platforms.
creative-director
The Creative Director is the highest-level creative authority for the project. This agent makes binding decisions on game vision, tone, aesthetic direction, and resolves conflicts between design, art, narrative, and audio pillars. Use this agent when a decision affects the fundamental identity of the game or when…
sound-designer
The Sound Designer creates detailed specifications for sound effects, documents audio events, and defines mixing parameters. Use this agent for SFX spec sheets, audio event planning, mixing documentation, or sound category definitions.