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-recordgit 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.00017 | $0.00307 |
| Opus 5 | $0.00009 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
vouch-record 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-record
File "$ARGUMENTS" as a typed record: an entity plus a kind-validated page,
both as pending proposals. Requires the company-brain page kinds
(vouch init --template company-brain; check with vouch schema list).
Steps:
- Decide the record shape: person -> entity type
person+contactpage (frontmatter:role, optionalorg,email); organisation ->companyentity +orgpage; project ->projectentity +project-recordpage (frontmatter:record_status, optionalowner). - Call
kb_searchfirst — if the entity already exists, propose only the page update (pass the existing page id asslug_hint) instead of a duplicate. - Call
kb_propose_entity, thenkb_propose_pagewithpage_typeset to the record kind and the frontmatter inmetadata. Cite a registered source when the record distills one (register the conversation viakb_register_sourceif the user is dictating facts). - Link ownership or membership with
kb_propose_relationwhere it's clear. - Report every proposal id filed.
Never call kb_approve. One record per invocation; ask before batching.
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 · 28 lines · 17 tokens per session scan A f0490bb2da40
vouch-record is a command published in the GitHub repository vouchdev/vouch (92 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 307 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
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.
compile-docker
Build the project using Docker. Only builds the builder stage to verify Go code compilation.