method

A command for planning research and agent handoffs around sound or listening. It identifies what evidence, references, methods, and follow-up work are needed.

In plain words
What is it for?
Use it for artistic research, listening exercises, essays, theses, workshops, fieldwork plans, and routing sound-related work to other agents, apps, datasets, or methods.
Why use it?
It helps turn a broad listening task into a clear plan, while checking which claims the available evidence can support. TDD is not involved here; the command is for sonic research and workflow planning.

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/method
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 657 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.00657
Opus 5 $0.00000 $0.00329
Sonnet 5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00066

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

Security

Grade A, and why

method 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/method.md · 70 lines

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.

/method

Purpose

/method is the sonic methodology command. It turns a listening situation into a research and agent-handoff plan: which ears to use, which evidence is available, which claims are permitted, which references matter, and what another agent or app should do next.

When To Use

Use /method for:

  • research design and artistic research
  • listening practice design
  • essays, theses, workshops, fieldwork plans, and project methods
  • agentic workflow planning
  • routing sonic tasks into other apps, agents, datasets, or frameworks
  • deciding whether the next step should be technical, perceptual, voice, audiovisual, access, field, forensic, political, fictional, or reference work

Skills Called

  • akouo-router
  • acoulogical-object-listening
  • critical-political-listening
  • accessibility-normative-listening
  • reference-layer

Execution Order

  1. Run akouo-router to identify evidence, risk, command route, primary mode, secondary mode, and corrective mode.
  2. Run acoulogical-object-listening to keep method grounded in the object rather than abstract theory.
  3. Run critical-political-listening to audit power, access, extraction, archive, labor, platform, and institutional stakes.
  4. Run accessibility-normative-listening to name implied listener, alternate access path, and missing testing.
  5. Run reference-layer to map concepts, methods, traditions, cautions, research routes, and adjacent modes.
  6. Synthesize as an operational plan for the next agentic workflow.

Expected Output

Use schemas/command-output.schema.json.

The output must include:

  • evidence inventory
  • permitted and forbidden claim types
  • proposed mode chain
  • methodology, references, and cautions
  • access requirements
  • handoff notes for another agent, app, or framework
  • recommended next mode or command

When the receiving system supports expanded routing plans, carry them in the optional routing_plan field (schemas/routing-plan.schema.json); the reference app emits this for /method so the handoff includes evidence level, claim permissions, and stop conditions.

Read the full file on GitHub · 70 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 · 70 lines · 0 tokens per session scan A 678538ffd255

Subscribe to this mod's changes

method 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 657 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.