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/techgit clone --depth 1 https://github.com/sonicfieldlabs/akouoWhat 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.00456 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
tech 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 3d 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.
/tech
Purpose
/tech is the technical inspection command. It focuses on file properties, signal behavior, waveform or spectrogram evidence, production artifacts, and mediation chains.
When To Use
Use /tech for:
- file properties
- waveform and spectrogram inspection
- mastering, mixing, or production notes
- clipping, distortion, noise, hum, hiss, dropouts, or codec artifacts
- audio repair planning
- metadata review
- AI audio artifacts
- sensor, microphone, compression, or platform mediation
Skills Called
akouo-routeras an implicit planning pass that supplies the evidence inventory, risks, and forbidden assumptions the synthesis must respectsignal-inspection-listeningtransductive-media-listeningwhen mediation, codecs, sensors, models, platforms, or conversion chains are relevant
Execution Order
- Run
signal-inspection-listening. - Run
transductive-media-listeningif the sound's capture, encoding, transformation, or model mediation matters. - Synthesize technical observations and state what cannot be measured from the available input.
Expected Output
Use schemas/command-output.schema.json.
The output must include:
- technical observations
- measured claims only when measurement exists
- inferred technical causes clearly marked
- mediation chain when known
- what remains technically undetermined
- recommended next mode
Guardrails
- Technical evidence is not cultural meaning.
- Do not invent file metadata or measurements.
- Do not overstate source identity from signal traits.
- If only text is supplied, state what technical inspection would require.
- Keep repair or production recommendations separate from evidence claims.
Must Not Do
- Do not place unverified values in
measured. - Do not claim exact microphone, plugin, codec, platform, or model unless known.
- Do not treat spectrogram patterns as proof of intention.
- Do not ignore transduction when the recording chain shapes the sound.
- Do not make forensic claims from technical artifacts alone.
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.
- 3d ago First seen · 64 lines · 0 tokens per session scan A 43c7b5de78ae
tech is a command published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 456 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.