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 sovereign-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/sovereign-listening)<a href="https://agentmods.dev/skills/sonicfieldlabs/akouo/sovereign-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/sovereign-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/sovereign-listening"><img src="https://agentmods.dev/badge/skills/sonicfieldlabs/akouo/sovereign-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.00211 | $0.02205 |
| Opus 5 | $0.00105 | $0.01103 |
| Sonnet 5 | $0.00042 | $0.00441 |
| Haiku 4.5 | $0.00021 | $0.00220 |
Grade A, and why
sovereign-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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sovereign-listening
Purpose
Every other AKOÚŌ mode disciplines what a listening may claim. This mode disciplines what a listening may do: which sounds it refuses before capture, which it releases after hearing, which aspects it declines to reveal, what it will not keep. It is the Rights of the Audible made operational — the right to silence, the right to opacity, the right of communities to their own protocols — as a runtime layer instead of a paragraph.
A listening covenant is the unit. It is written by a human in plain text, parsed into rules and commitments, and carried by the listening system. Rules are the executable subset (refuse this source, ignore that class, withhold this aspect, retain nothing, blur the place, close the ear at night). Commitments are everything else the author asked for — lines no engine can yet execute — kept verbatim, reported with every hearing, addressed to humans and to future machines. The covenant is a bridge, not a cage: it does not make the machine obedient; it makes the machine answerable, because what was asked, what was enforced, and what was withheld are all on the record.
When To Use
Use sovereign-listening when:
- a covenant document is active for the host, session, project, or place
- recording or listening happens under a community protocol (ancestral, sacred, endangered, or place-bound sound)
- a deployment must honor the right to silence (some things go unheard) or the right to opacity (some things are heard but never decoded or revealed)
- a household, clinic, classroom, shelter, or workplace wants listening without retention, or hearing without identification
- a habitat is monitored under an ecological protocol — the flood and the fire, not the bedroom; the species count, not one decibel more
- another agent's listening should be audited against a declared covenant: did the hearing respect what was asked?
Do NOT use it to launder censorship as care: a covenant governs the listener that adopted it, protecting the listened-to; it is not a tool for silencing third parties. If a rule's purpose is to hide the listener's own accountability, refuse the framing and say so.
What ships with it
8 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/covenant.schema.json 4.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 · 101 lines · 211 tokens per session scan A b48f609800e1
sovereign-listening is a skill published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 1mo ago), licensed MIT. It adds 211 tokens to every session and 2,205 once invoked, about $0.0011 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…