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/forensicgit 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/forensic)<a href="https://agentmods.dev/commands/sonicfieldlabs/akouo/forensic"><img src="https://agentmods.dev/badge/commands/sonicfieldlabs/akouo/forensic.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.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
forensic 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forensic
Purpose
/forensic is the strict evidentiary command. It treats sound as trace, testimony, archive, memory, damage, or possible evidence while refusing narrative completion.
When To Use
Use /forensic for:
- recordings of violence
- testimony
- archives
- surveillance audio
- protest recordings
- damaged material
- oral history
- legal or quasi-legal contexts
- political recordings where overclaiming may cause harm
- authentication caution
Skills Called
akouo-routeras an implicit planning pass that supplies the evidence inventory, risks, and forbidden assumptions the synthesis must respectsignal-inspection-listeningforensic-archival-listeningcritical-political-listeningas corrective
Execution Order
- Run
signal-inspection-listeningto identify available technical evidence and limits. - Run
forensic-archival-listeningto separate audible evidence, measured evidence, inference, interpretation, speculation, and unknowns. - Run
critical-political-listeningto identify archive, testimony, surveillance, policing, colonial, institutional, or evidentiary stakes. - Synthesize conservatively.
Expected Output
Use schemas/command-output.schema.json.
The output must include:
- available evidence
- missing evidence
- chain of mediation when known
- significant silences or damage
- confidence limits
- claims separated by taxonomy
- what cannot be responsibly concluded
Guardrails
- Evidence requires restraint.
- Speculative claims should normally be empty.
- Technical observations can support evidence but cannot complete a story alone.
- Political context matters, but it must not override evidentiary limits.
- The output should use plain, cautious language.
Must Not Do
- Do not invent evidence.
- Do not identify speakers, locations, weapons, events, or sequences without support.
- Do not treat background sounds as proof without corroboration.
- Do not use poetic language by default.
- Do not convert testimony into symbolic fiction.
- Do not make legal conclusions.
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 · 70 lines · 0 tokens per session scan A 6607e539d8da
forensic 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 478 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
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.
graphite-morphology-classify
Classify graphite in a cast-iron micrograph per ASTM A247 / ISO 945-1, quantify nodularity, and read the matrix — the single most diagnostic observation in a cast-iron case.