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 musical-aesthetic-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/musical-aesthetic-listening)<a href="https://agentmods.dev/skills/sonicfieldlabs/akouo/musical-aesthetic-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/musical-aesthetic-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/musical-aesthetic-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/musical-aesthetic-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.00182 | $0.02485 |
| Opus 5 | $0.00091 | $0.01242 |
| Sonnet 5 | $0.00036 | $0.00497 |
| Haiku 4.5 | $0.00018 | $0.00248 |
Grade A, and why
musical-aesthetic-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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
musical-aesthetic-listening
Purpose
musical-aesthetic-listening is the ear for musical structure, aesthetic force, and creative usefulness. It listens for pulse, rhythm, meter, pitch, interval, harmony, melody, timbre, texture, density, contour, repetition, form, production gesture, and poetic/aesthetic affordance.
This mode exists because music and sound design often need more than technical signal inspection or generic perceptual description. It asks what the sound is doing musically and aesthetically while refusing lazy genre naming, exoticization, or symbolic inflation.
When To Use
Use this skill for:
- songs, beats, loops, drones, melodies, chords, bass lines, rhythms, and musical fragments
- sound design samples that need creative or production-useful description
- electroacoustic, experimental, ambient, club, pop, noise, AI-generated, or synthetic musical material
- pitch, interval, tuning, harmony, melody, contour, meter, tempo, groove, repetition, and form questions
- aesthetic language, mood, atmosphere, energy, or poetic description when it must remain grounded
- music benchmark cases where the agent must avoid hallucinated audio, genre overreach, and prompt parroting
- cultural or tonal caution around modality, tuning systems, rhythmic patterns, instruments, and traditions
Core Question
What can be responsibly said about this sound's musical organization, aesthetic force, and creative usefulness from the evidence available?
Conceptual Refinements
- Musical organization is not genre membership: rhythm, pitch, timbre, texture, and form can be described before any style, scene, or tradition is named.
- Aesthetic force is an interpretation of grounded traits, not a property of the file; poetic language earns its place only when tied to musical detail.
- Sound-design utility is a creative affordance claim, not evidence of intention, authorship, or production chain.
- Tonal and rhythmic materials travel across cultures; pentatonicism, drones, or syncopation alone cannot assign geography, ethnicity, period, or sacredness.
- Prompt text, model captions, measured signal, and heard audio support different musical claims; keep the evidence source attached to each claim.
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 · 159 lines · 182 tokens per session scan A 7c561890b742
musical-aesthetic-listening is a skill published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 2,485 once invoked, about $0.0009 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…