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-followupgit 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.00014 | $0.00263 |
| Opus 5 | $0.00007 | $0.00131 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
vouch-followup 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 3d 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-followup
File "$ARGUMENTS" as a followup page proposal — a commitment with a due
date that vouch digest lists until it's closed. Requires the company-brain
page kinds (vouch init --template company-brain).
Steps:
- Extract what's owed, by whom, and when. If no due date is stated, ask — an undated followup never surfaces.
- Call
kb_propose_pagewithpage_type: "followup", a short imperative title, andmetadata:due_at(ISO date),followup_status: "open",ownerwhen known. Put context in the body; cite a source id if the commitment came from a registered conversation or document. - To close or move one later: re-propose the same page (
slug_hint: <page id>) withfollowup_status: "done"(or a newdue_at) — status changes go through the gate like any other edit. - Report the proposal id and the due date filed.
Never call kb_approve.
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.
- 3d ago First seen · 25 lines · 14 tokens per session scan A 3f68c1c4ce15
vouch-followup is a command published in the GitHub repository vouchdev/vouch (91 stars, last pushed 11d ago), licensed MIT. It adds 14 tokens to every session and 263 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
loop
Iteratively fix issues until all resolved or max iterations reached.
errors
You are pulling end-user error/exception reports stored by the ct-analytics Cloudflare Worker (D1 table errors) and writing a human-readable summary inline. Errors are populated by POST /errorreport from three sources: rustpanic, rustcommand, frontend. Retention is 90 days.
changelog
Generate a changelog for version $ARGUMENTS by analyzing git history.
daily
Read agentbrain/skills/daily-consolidation.md and execute the full daily consolidation cycle. This is the end-of-day "sleep" — consolidate and learn from today's work.
gsd:list-phase-assumptions
Surface Claude's assumptions about a phase approach before planning.
git
Git operations with intelligent commit messages and workflow optimization.