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/punt-labs/vox/voicegit clone --depth 1 https://github.com/punt-labs/voxWrote 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/punt-labs/vox/voice)<a href="https://agentmods.dev/commands/punt-labs/vox/voice"><img src="https://agentmods.dev/badge/commands/punt-labs/vox/voice.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.00010 | $0.00481 |
| Opus 5 | $0.00005 | $0.00241 |
| Sonnet 5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
voice 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 4d 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.
What it actually says
/vox:voice command
Set the session voice. No argument opens a picker from the current provider's
featured voices; a name (with an optional stray leading @ stripped) writes
it to the session and to .punt-labs/vox/vox.md.
Usage
/vox:voice— pick from the featured voices for the current provider/vox:voice matilda— set session voice tomatilda/vox:voice @matilda— the@is stripped (a common typo)
Implementation
First normalize $ARGUMENTS: strip a leading @ if present (a user may type
@matilda out of habit) and trim whitespace. Treat a lone @ or an empty
string as no argument.
- (no argument):
- Call the
voiceMCP tool with no arguments to get{"provider", "current", "available", "featured"}. - If
featuredis empty or has fewer than 2 entries, callvoicewithname=<current>(or just skip the picker) and stop. - Otherwise build a candidate list capped at 4: start with
current(if set), then append entries fromfeatured, de-duplicating by name. CallAskUserQuestionwith one question:question:"Which voice?"header:"Voice"multiSelect: falseoptions:label=<name>,description=<blurb-from-featured>; the current selection's description is suffixed" (current)".
- On the user's pick, call
voiceagain withname=<pick>. No text output — the panel confirms.
- Call the
<name>: Call thevoiceMCP tool withname="<name>"directly. The server strips a stray@sigil and writes the normalized name. No text output.
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.
- 4d ago First seen · 43 lines · 10 tokens per session scan A a5de0bf61091
voice is a command published in the GitHub repository punt-labs/vox (3 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 481 once invoked, about $0.0001 per session on Opus 5. 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
meeting-listen
Play back a completed meeting summary as a voiced debate between personas.
meeting-hive
Run an autonomous PR/FAQ review meeting where four personas debate and reach consensus without user intervention.
vote
Assess whether a PR/FAQ should move forward with a structured go/no-go decision.
feedback
Incorporate feedback into PR/FAQ and redraft affected sections.
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
badge
Generate a stage-colored badge and embed it in your README.