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 symbolic-fictional-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/symbolic-fictional-listening)<a href="https://agentmods.dev/skills/sonicfieldlabs/akouo/symbolic-fictional-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/symbolic-fictional-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/symbolic-fictional-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/symbolic-fictional-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.00141 | $0.02015 |
| Opus 5 | $0.00071 | $0.01007 |
| Sonnet 5 | $0.00028 | $0.00403 |
| Haiku 4.5 | $0.00014 | $0.00201 |
Grade A, and why
symbolic-fictional-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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
symbolic-fictional-listening
Purpose
symbolic-fictional-listening is the speculative ear of akoúō. It interprets sound through symbolic systems, myth, cosmology, sonic fiction, hallucination, futurity, ritual, dream, alien voice, synthetic worlds, and hyperstition.
This mode permits imagination as method, but only inside declared speculative boundaries.
When To Use
Use this skill for:
- sonic fiction
- speculative sound worlds
- alien voice
- mythic sound
- ritual sound
- religious or cosmogonic sound
- hyperstition
- fictional audio prompts
- game sound
- film worlds
- dreamcore
- ambient fantasy
- AI hallucinated sonic descriptions
- symbolic reading of musical or sonic material
- creative writing, sound design briefs, and worldbuilding
Core Question
What world does this sound imply, invoke, haunt, worship, simulate, or invent?
Conceptual Refinements
- Sonic fiction is a method, not decoration: it lets sound generate concepts, worlds, and temporalities while keeping evidence boundaries intact.
- Mythscience can intensify impossible histories and speculative systems, but it must not masquerade as scholarship or forensic fact.
- Sonic possible worlds ask what reality the sound makes actual for a listener, without claiming that world is externally verified.
- Hauntology, remanence, ghosts, lost futures, and dead media should be handled as symbolic or cultural readings unless evidence supports archival claims.
- Hallucination-as-glitch can reveal generative assumptions in AI audio or perception, but it does not prove hidden messages, entities, or intent.
Input Assumptions
This skill can work with:
- audio files
- sound prompts
- fictional descriptions
- game, film, installation, or narrative contexts
- AI-generated sonic captions
- music or sound design fragments
- ritual, mythic, symbolic, or dreamlike material
- obsolete media, hauntological textures, glitches, or speculative AI outputs
If the input is fictional or prompted, the skill must identify it as such. If real audio is present, the skill must separate actual audible traits from speculative worldbuilding.
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 · 167 lines · 141 tokens per session scan A ae50d97773f1
symbolic-fictional-listening is a skill published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 1mo ago), licensed MIT. It adds 141 tokens to every session and 2,015 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…