reference

A command that connects a sound or listening report with ideas, research methods, authors, traditions, and related practices. It maps possible directions for studying or developing the sound.

In plain words
What is it for?
Use it for sound-studies research, sonic methods, thesis or essay planning, and linking listening work to topics such as voice, accessibility, field recording, or audiovisual media.
Why use it?
It helps turn listening into a structured research path instead of an unconnected list of references. It also points out assumptions and risks of making claims that the sound does not support.

Command

Install

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.

agentmods
npx agentmods add commands/sonicfieldlabs/akouo/reference
Clone the repo
git clone --depth 1 https://github.com/sonicfieldlabs/akouo
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 482 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00482
Opus 5 $0.00000 $0.00241
Sonnet 5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

Measured 2d ago against content hash 9d32b4f98e47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reference 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 2d 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.

commands/reference.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/reference

Purpose

/reference maps a sonic object or prior listening output to concepts, methodologies, authors, traditions, cautions, adjacent modes, and research routes.

It is not a bibliography generator. It is a conceptual mapping layer.

When To Use

Use /reference for:

  • sound studies research routes
  • sonic methodologies
  • author and tradition mapping
  • conceptual clarification
  • thesis, essay, or project development
  • connecting a listening report to adjacent methods
  • routing concepts for voice, audiovisual, accessibility, field, material, and agentic listening workflows
  • identifying cautions before deeper interpretation

Skills Called

  • akouo-router as an implicit planning pass when the map is requested as a command output
  • reference-layer
  • optionally any prior listening output from another mode or command

Execution Order

  1. Run akouo-router to identify evidence, risk, and forbidden assumptions.
  2. Identify the object or prior listening output.
  3. Identify triggered concepts and methodological problems.
  4. Map relevant authors, traditions, and sonic practices.
  5. Identify possible research routes.
  6. Identify cautions and overclaiming risks.
  7. Recommend adjacent listening modes.

Expected Output

Use schemas/command-output.schema.json when wrapped as a command result.

The reference map should include:

  • concepts triggered
  • sonic methodologies
  • authors or traditions
  • possible research routes
  • research questions
  • cautions
  • adjacent modes
  • recommended next mode

Guardrails

  • References must clarify the listening situation.
  • Prefer conceptual relevance over quantity.
  • Map methods and questions, not only names.
  • Include cautions, not only affinities.
  • Keep references tied to the actual sound, prompt, archive, or prior output.
  • State when the available input is too thin for confident reference mapping.

Must Not Do

  • Do not produce a random reading list.
  • Do not decorate weak analysis with famous names.
  • Do not imply that a reference proves an interpretation.
  • Do not erase nonhuman, embodied, technical, archival, political, or speculative dimensions.
  • Do not collapse method into bibliography.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 2d ago First seen · 73 lines · 0 tokens per session scan A 9d32b4f98e47

Subscribe to this mod's changes

reference is a command published in the GitHub repository sonicfieldlabs/akouo (10 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 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.