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/recapgit 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/recap)<a href="https://agentmods.dev/commands/punt-labs/vox/recap"><img src="https://agentmods.dev/badge/commands/punt-labs/vox/recap.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.00007 | $0.00199 |
| Opus 5 | $0.00003 | $0.00100 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
recap 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:recap command
Speak a brief summary of the last response.
Usage
/vox:recap
Implementation
- Look at your most recent response (before this command) — the one the user wants summarized.
- Extract the 2-3 most important points: what changed, what was done, any key findings.
- Write the summary as clear, concise spoken text (30 seconds when spoken, roughly 60-80 words).
- Call the
unmuteMCP tool with:text: your summaryephemeral:true
- Show the summary text in the conversation as well (voice supplements text, never replaces it).
Keep the summary factual. No filler words. No "Here's a summary of..." preamble — just the content.
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 · 25 lines · 7 tokens per session scan A 85d78643dffa
recap is a command published in the GitHub repository punt-labs/vox (3 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 199 once invoked, about $0.0000 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.