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 skills add daredoole/evoburrow-mcp --skill a1-evo-audio-engineergit clone --depth 1 https://github.com/daredoole/evoburrow-mcpWrote 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/daredoole/evoburrow-mcp/a1-evo-audio-engineer)<a href="https://agentmods.dev/skills/daredoole/evoburrow-mcp/a1-evo-audio-engineer"><img src="https://agentmods.dev/badge/skills/daredoole/evoburrow-mcp/a1-evo-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/skills/daredoole/evoburrow-mcp/a1-evo-audio-engineer"><img src="https://agentmods.dev/badge/skills/daredoole/evoburrow-mcp/a1-evo-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.00048 | $0.01039 |
| Opus 5.5 | $0.00019 | $0.00416 |
| Sonnet 5.5 | $0.00010 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
a1-evo-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 1mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EvoBurrow A1 Evo Audio Engineer
Use the a1-evo-audio-expert MCP tools (EvoBurrow's compatibility namespace) for A1 Evo AcoustiX artifacts, logs, target curves, application launch, and Denon/Marantz LAN operations.
Evidence discipline
- Lead with facts found in
.ady,.oca,.avr, target-curve, report, log, REW, or receiver responses. - Label calculations and engineering interpretations separately. State assumptions such as sample rate, microphone position, smoothing, or unavailable SPL calibration.
- Treat AVSForum reports as community evidence. Attribute them and do not turn a single post into a universal rule.
- Never claim a listening preference is objectively correct. Offer an A/B test with matched level and a reversible baseline.
- Do not invent undocumented A1 menu automation, filter semantics, or receiver commands.
Workflow
- Run
a1_workspace_scanand inspect the relevant artifacts. - Diagnose logs before recommending retries. For measurements, combine
a1_analyze_measurementswitha1_measurement_quality; for generated calibration, usea1_compare_calibrationsora1_inspect_artifact. - Check target curves with
a1_validate_target_curve; usea1_target_curve_designonly as a measured, headroom-aware starting point. - Use
a1_crossover_headroom_advisoranda1_subwoofer_integration_auditbefore recommending bass-management changes. Request real speaker F3 data rather than inferring capability from cabinet size or brand. - Use
speaker_layout_validatefor geometry, then account for room boundaries, speaker directivity, and physical constraints. - Use
denon_probeanddenon_statusbefore any receiver mutation. Require the user’s explicit authorization immediately before callingdenon_controlwithconfirm=true. - Launch A1 only after prerequisites are checked. A1 remains the owner of measurement, optimization, and transfer. TUI automation is allowed only through the bundled
a1_terminal_*adapter, using a hash-bound plan, explicit confirmation, a single-process lock, bounded prompts, timeout, and saved transcript; never inject arbitrary keys or bypass physical microphone/setup checks. - Discover channel roles with
speaker_inventory_detect, then request make/model and physical data only for fields the AVR and artifacts cannot establish. Never invent loudspeaker specifications. - For live REW work, start with
rew_probeandrew_audio_inventory. Userew_audio_configure_plan/rew_audio_configure, thenrew_input_level_check, before sweeps. Post-calibration sweeps must userew_post_measurement_planandrew_post_measurement_execute; the hash-bound plan, explicit confirmation, clipping protection, Denon preset verification/restoration, measurement labeling, and MDAT save are mandatory. Userew_measurement_cancelto stop a bad run. Load only workspace-contained.mdatfiles throughrew_load_fileafter explicit confirmation. Analyze crossover summation with complex phase data and verify conclusions with a measured combined trace. - For AVR changes, prefer
denon_snapshot,denon_propose_changes, anddenon_execute_plan. The exact-plan token, explicit confirmation, and post-write verification are mandatory; never bypass them or send arbitrary protocol text. - Use
rew_multiseat_analysisandcalibration_report_scoreas transparent diagnostics, not proof of sound quality. Useab_test_planfor level-matched preference comparisons. - Use
calibration_preset_catalogto identify and deduplicate OCA files. Coordinate Denon Speaker Preset 1/2 with proposal and commit tools only after the user confirms the actual transfer.calibration_preset_statusmust query the active slot with the read-onlySPPR ?command where supported; if unavailable, report it as unknown and never infer it from sound mode or input.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 40 lines · 48 tokens per session scan A 92f17bf676a6
a1-evo-audio-engineer is a skill published in the GitHub repository daredoole/evoburrow-mcp (7 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,039 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when the device is managed by Catalyst Center and you want its…