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-propose-from-prgit 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.00010 | $0.00251 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
vouch-propose-from-pr 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-propose-from-pr
A PR is a decision: someone proposed a change, the team accepted it. The "why" gets compressed into the merge message and forgotten. This command preserves the why as cited claims in the KB.
Steps:
- Parse
$ARGUMENTSas a PR URL or<owner>/<repo>#<num>; default to the most-recently-merged PR you authored. - Fetch the PR title, body, and the merged-commit SHA via
gh. - Register the merge commit as a
kb_register_sourceso subsequent claims can cite it. - Read the diff. For each behavioural change (not formatting / renaming),
draft one
kb_propose_claimwhose text summarises the new invariant the code now upholds, citing the source from step 3. - Propose at most five claims per PR. If a PR is that big, suggest the contributor split it next time.
Do not auto-approve. The KB's review gate is intentional; this command only fills the queue.
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 · 26 lines · 10 tokens per session scan A baac97b21b2f
vouch-propose-from-pr is a command published in the GitHub repository vouchdev/vouch (91 stars, last pushed 10d ago), licensed MIT. It adds 10 tokens to every session and 251 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
checkpoint
Create a git checkpoint to safely save current progress.
git-commit
Create a git commit for the current changes using Conventional Commits-style format.
commit
Create a git commit with a well-structured message.
commit
Commit current changes. User input: $ARGUMENTS.
commit
Создать git commit с правильным сообщением.
git
Add all changes to git. Commit changes. Push to remote.