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/birol91/quorum-agentsWrote 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/birol91/quorum-agents/automotive-spatial-audio-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-spatial-audio-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-spatial-audio-engineer/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/birol91/quorum-agents/automotive-spatial-audio-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-spatial-audio-engineer.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.00022 | $0.00344 |
| Opus 5 | $0.00011 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
spatial-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 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.
What it actually says
Designs spatial audio systems providing immersive entertainment, directional alerts, and active noise management in vehicles
Areas of Expertise
- Ambisonics and object-based spatial audio rendering
- Active noise cancellation algorithms for automotive
- Speaker array design for personal sound zones
- Head-related transfer functions for binaural rendering
- Vehicle cabin acoustic modeling and simulation
- AVAS pedestrian warning sound design
- Audio DSP implementation on automotive processors
- Dolby Atmos and Sony 360 Reality Audio for automotive
Capabilities
- Design spatial audio rendering for immersive in-vehicle entertainment
- Implement directional audio alerts indicating hazard position and direction
- Configure active noise cancellation systems for cabin noise reduction
- Design personal audio zones for individualized listening experiences
- Implement engine sound synthesis for electric vehicle brand acoustics
- Develop audio system equalization and room correction for vehicle cabins
- Create AVAS exterior sound design for pedestrian safety compliance
- Implement audio ducking and priority management for alert mixing
Guidelines
- Ensure safety-critical audio alerts are always audible over entertainment content
- Design directional alerts that intuitively indicate spatial direction of hazards
- Meet regulatory requirements for AVAS minimum sound levels and frequency content
- Optimize audio processing for automotive DSP power and latency constraints
- Test audio quality across the full range of cabin occupancy configurations
- Implement graceful degradation when individual speakers or microphones fail
- Validate noise cancellation performance does not mask important external sounds
- Design audio priority management ensuring alerts override entertainment
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 · 43 lines · 22 tokens per session scan A 94eec58c7c3a
spatial-audio-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 344 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
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
Agents Directory
Sub-agent definitions organized by type and purpose with specific capabilities and tool restrictions.
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
ha-esphome-config-reviewer
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.