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 sonicfieldlabs/akouo --skill material-event-listeninggit clone --depth 1 https://github.com/sonicfieldlabs/akouoWrote 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/sonicfieldlabs/akouo/material-event-listening)<a href="https://agentmods.dev/skills/sonicfieldlabs/akouo/material-event-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/material-event-listening/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/sonicfieldlabs/akouo/material-event-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/material-event-listening.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.00150 | $0.02087 |
| Opus 5 | $0.00075 | $0.01043 |
| Sonnet 5 | $0.00030 | $0.00417 |
| Haiku 4.5 | $0.00015 | $0.00209 |
Grade A, and why
material-event-listening 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 12d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
material-event-listening
Purpose
material-event-listening is the ear for sound as matter, vibration, duration, process, and event. It corrects the tendency to treat sound only as source, signal, object, meaning, or style.
This mode listens for what unfolds, resonates, propagates, decays, accumulates, and acts through bodies, rooms, devices, materials, and time.
When To Use
Use this skill for:
- drones, noise, feedback, resonance, hum, rumble, and sustained vibration
- microsound, grains, clicks, bursts, discontinuities, and event density
- sound sculptures, installations, loudspeakers, instruments, physical interfaces, and material sound art
- sub-bass, ultrasound, infrasound, unsound, tactile vibration, and pressure
- weather, engines, machines, infrastructure, geological or architectural sound
- questions about duration, process, flux, emergence, decay, and material agency
- cases where acoulogical object listening feels too static or source-centered
- sonic ontology or methodology questions about object versus event
Core Question
What material event is unfolding, and what does it do across bodies, spaces, devices, and time?
Conceptual Refinements
- Sound can be approached as event rather than object: something that unfolds, persists, decays, and recurs instead of something that simply is.
- Distinguish extensive traits (frequency, amplitude, duration, position) from intensive traits (density, force, grain, pressure); only the first are measurable, and the second must be marked as interpretation.
- Vibration is materially real but epistemically demanding: infrasound, ultrasound, and tactile vibration require measurement or playback context before any bodily-effect claim.
- Material supports are part of the sound: loudspeakers, rooms, surfaces, instruments, bodies, air, and water are agents in the event, not passive containers.
- Sonic materialism is a productive corrective to meaning-first listening, but it must not become a new mysticism; ontology never substitutes for evidence.
What ships with it
7 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.
- references/claim-taxonomy.schema.json 5.3 KB
- references/ensemble.schema.json 1.8 KB
- references/listening-context.schema.json 7.7 KB
- references/listening-output.schema.json 11 KB
- references/listening-pass.schema.json 2.4 KB
- references/listening-provenance.schema.json 3.9 KB
- references/route-decision.schema.json 1.8 KB
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.
- 12d ago First seen · 146 lines · 150 tokens per session scan A 5494b574db3a
material-event-listening is a skill published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 1mo ago), licensed MIT. It adds 150 tokens to every session and 2,087 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…