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 agentmods add commands/sonicfieldlabs/akouo/routegit 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/route)<a href="https://agentmods.dev/commands/sonicfieldlabs/akouo/route"><img src="https://agentmods.dev/badge/commands/sonicfieldlabs/akouo/route.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00498 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
route 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 5d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/route
Purpose
/route is the router-only handoff command. It produces a compact listening plan that another agent, app, framework, or workflow can execute without running a full listening analysis.
When To Use
Use /route for:
- agentic workflow orchestration
- routing audio, transcript, video, field note, dataset, metadata, or model output into AKOÚŌ skills
- deciding primary, secondary, and corrective listening modes
- producing a stop-condition list before autonomous work begins
- integrating AKOÚŌ with other apps, skill systems, benchmark runners, or model routers
Skills Called
akouo-router
Execution Order
- Identify input type and available evidence.
- Score likely listening frames.
- Select primary, secondary, and corrective modes.
- State risks and forbidden assumptions.
- Recommend command, next mode, and handoff conditions.
Expected Output
Use schemas/router-output.schema.json.
When the receiving system supports expanded routing plans, also use schemas/routing-plan.schema.json. When the result is wrapped as a command output, the expanded plan travels in the optional routing_plan field of schemas/command-output.schema.json; the reference app emits it this way, deriving claim_permissions from the router's Evidence Ladder. See examples/routing-plan-example.json.
The output must include:
- object listened to
- input type
- available and unavailable evidence
- primary, secondary, and corrective modes
- route reasoning
- risks and must-not-assume list
- recommended command and next mode
Guardrails
/routedoes not analyze the sound.- It must not make content claims that belong to listening modes.
- It must preserve claim discipline by naming evidence limits and stop conditions.
- It must be portable across agent frameworks.
- It must not include private file paths, private notes, credentials, unpublished source maps, or local project data.
Must Not Do
- Do not pretend routing is analysis.
- Do not skip corrective mode selection.
- Do not treat prompt, transcript, metadata, and audio as equivalent evidence.
- Do not recommend unsupported measurements.
- Do not hide uncertainty to make the plan appear autonomous.
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.
- 5d ago First seen · 64 lines · 0 tokens per session scan A f0c40ebe59a4
route is a command published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 498 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.
Other commands, from other repositories
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
simulation-calibrator
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.