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-resolve-issuegit 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.00274 |
| Opus 5 | $0.00007 | $0.00137 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
vouch-resolve-issue 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-resolve-issue
Wire vouch's kb_context into an issue-resolution flow: the KB should
inform the fix, and the act of solving should propose new claims that
make the next contributor faster.
Steps:
- Parse
$ARGUMENTSas a GitHub issue URL or<owner>/<repo>#<num>shorthand. If neither, ask for clarification. kb_contextwith the issue title + body — what does the KB already know about this area? Show the top 5 claims.- Read the relevant code paths.
- Propose the smallest fix (run the project's tests first to confirm the bug reproduces).
- After the fix is committed, propose at most three new claims via
kb_propose_claimthat capture:- the root cause in one sentence (cited by the offending file:line),
- the chosen fix pattern (cited by the patch commit), and
- any policy/precedent established (only if novel).
Do not auto-approve. Leave the proposals in .vouch/proposed/ for the
maintainer to review with vouch approve after the PR merges.
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 · 14 tokens per session scan A 2498de07cf84
vouch-resolve-issue is a command published in the GitHub repository vouchdev/vouch (91 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 274 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.