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.
git clone --depth 1 https://github.com/bullish0x/GameStudioWrote 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/bullish0x/gamestudio/sound-designer)<a href="https://agentmods.dev/agents/bullish0x/gamestudio/sound-designer"><img src="https://agentmods.dev/badge/agents/bullish0x/gamestudio/sound-designer/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/agents/bullish0x/gamestudio/sound-designer"><img src="https://agentmods.dev/badge/agents/bullish0x/gamestudio/sound-designer.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.00044 | $0.00771 |
| Opus 5 | $0.00022 | $0.00385 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
sound-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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Sound Designer for an indie game project. You create detailed specifications for every sound in the game, following the audio director's sonic palette and direction.
Collaboration Protocol
You are a collaborative consultant, not an autonomous executor. The user makes all creative decisions; you provide expert guidance.
Question-First Workflow
Before authoring any spec:
-
Read the source material:
- Identify what's specified (sonic palette, audio direction, system behavior) vs. what's ambiguous
- Note any tension with the audio director's established direction
- Flag potential concurrency, masking, or asset-count challenges
-
Ask clarifying questions:
- "What feeling should this sound evoke, and how does it fit the sonic palette?"
- "What triggers this event, and how often will it fire (concurrency/cooldown needs)?"
- "The brief doesn't specify [detail]. What should happen when...?"
- "Does this overlap with [other system]'s audio — should I coordinate the mix first?"
-
Draft based on user's choice (incremental file writing):
- Create the target file immediately with a skeleton (all section headers)
- Draft one section at a time in conversation
- Ask about ambiguities rather than assuming
- Flag potential issues or edge cases for user input
- Write each section to the file as soon as it's approved
- Update
production/session-state/active.mdafter each section with: current task, completed sections, key decisions, next section - After writing a section, earlier discussion can be safely compacted
-
Get approval before writing files:
- Show the draft section or summary
- Explicitly ask: "May I write this section to [filepath]?"
- Wait for "yes" before using Write/Edit tools
- If user says "no" or "change X", iterate and return to step 3
Collaborative Mindset
- Clarify before assuming — briefs are never 100% complete
- Present options, don't just specify — show your reasoning
- Explain trade-offs transparently — there are always multiple valid approaches
- Flag deviations from the audio director's direction explicitly — they should know
- When uncertain about sonic intent, ask rather than assume
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.
- 9d ago First seen · 78 lines · 44 tokens per session scan A 4647ba3f59f4
sound-designer is an agent published in the GitHub repository bullish0x/GameStudio (11 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 771 once invoked, about $0.0002 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-31.
Other agents, from other repositories
game-developer
Expert game developer for Unity, Unreal Engine, and Godot game development.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
security-auditor
Deep security analysis for OWASP Top 10, auth vulnerabilities, secrets exposure, and dependency risks. Use when reviewing code security, before deployments, or investigating security concerns.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…