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.
git 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/commands/sonicfieldlabs/akouo/litany)<a href="https://agentmods.dev/commands/sonicfieldlabs/akouo/litany"><img src="https://agentmods.dev/badge/commands/sonicfieldlabs/akouo/litany/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/commands/sonicfieldlabs/akouo/litany"><img src="https://agentmods.dev/badge/commands/sonicfieldlabs/akouo/litany.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.00000 | $0.00566 |
| Opus 5.5 | $0.00000 | $0.00226 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
litany 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 2mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/litany
Purpose
/litany audits audiovisual and sonic analysis for simplistic binaries, especially claims that idealize sound against vision, writing, media, or technology.
It functions as an anti-mystification command.
When To Use
Use /litany for:
- audiovisual work
- film, video, and installation analysis
- game, interface, caption, subtitle, and scene analysis
- media theory
- critiques of sonic mysticism
- claims about sound as immersion, body, presence, authenticity, or liberation
- claims that oppose sound and vision too neatly
- checking a draft analysis for audiovisual litany patterns
Skills Called
akouo-routeras an implicit planning pass that supplies the evidence inventory, risks, and forbidden assumptions the synthesis must respectcritical-political-listeningtransductive-media-listeningaudiovisual-scenic-listeningacoulogical-object-listeningwhen needed to reground the critique in the sound object
Execution Order
- Run
critical-political-listeningto detect universalist, romantic, or binary assumptions. - Run
transductive-media-listeningto identify media, platform, apparatus, and conversion conditions. - Run
audiovisual-scenic-listeningto map sound-image-text-scene relations, synchronization, captions, and interface conditions. - Run
acoulogical-object-listeningwhen the critique needs to return to the perceptual sound object. - Produce an audit of litany patterns, anti-litany corrections, and remaining risks.
Expected Output
Use schemas/command-output.schema.json.
The output must identify whether the analysis reproduces binaries such as:
- sound is immersive, vision is distant
- sound is body, image is intellect
- sound is presence, writing is absence
- sound is South, vision is North
- sound is authentic, visuality is artificial
Guardrails
- Critique must be concrete and text-specific or object-specific.
- Do not reject embodiment, immersion, or presence automatically. Audit overstatement.
- Name the mediation that complicates the binary.
- Return to the sound object when critique becomes abstract.
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.
- 2mo ago First seen · 68 lines · 0 tokens per session scan A b864850cbe4a
litany is a command published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 566 tokens. 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.
litany compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| litanysonicfieldlabs/akouo | Command | 10 | 2d ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |