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/vouchdev/vouch/vouch-standupgit clone --depth 1 https://github.com/vouchdev/vouchWhat 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.00018 | $0.00227 |
| Opus 5 | $0.00009 | $0.00113 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
vouch-standup 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.
What it actually says
/vouch-standup
Give the user a morning briefing from the KB, then get out of the way.
Steps:
- Call the
kb_digestMCP tool (or runvouch digest --format markdownvia Bash if MCP is unavailable). Default window is fine unless the user names one. - Narrate it in four short lines, leading with counts: pending proposals
(oldest first — nudge
vouch reviewif any), decisions since the window start, stale claims worth akb_confirmor supersede, and followups due (with owners). - If a followup in the list is done, offer to file the close — a
kb_propose_pagewith the page's id asslug_hintandfollowup_status: "done"— but only on explicit confirmation.
Read-only otherwise. Never call kb_approve; reviewing is the human's job.
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.
- 2d ago First seen · 23 lines · 18 tokens per session scan A 6a487c2f7eab
vouch-standup is a command published in the GitHub repository vouchdev/vouch (91 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 227 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-30.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
validate-gap
Analyze implementation gap between requirements and existing codebase.
spec-impl
Execute spec tasks using TDD methodology.
security-dialogs
Deep AI-based credential scan for dialog files.
security
Провести аудит безопасности кода.
gsd:list-phase-assumptions
Surface Claude's assumptions about a phase approach before planning.