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.
git clone --depth 1 https://github.com/vouchdev/vouchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/vouchdev/vouch/vouch-resolve-issue)<a href="https://agentmods.dev/commands/vouchdev/vouch/vouch-resolve-issue"><img src="https://agentmods.dev/badge/commands/vouchdev/vouch/vouch-resolve-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/vouchdev/vouch/vouch-resolve-issue"><img src="https://agentmods.dev/badge/commands/vouchdev/vouch/vouch-resolve-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00014 | $0.00274 |
| Opus 5.5 | $0.00006 | $0.00110 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (72 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 274 once invoked, about $0.0001 per session on Opus 5.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
fix
A code-repair command that detects and fixes errors reported by language servers, linters, or type checkers. These tools find code problems such as invalid syntax, style issues, and mismatched data types.
gate
Dispatch the moai workflow gate with: $ARGUMENTS.
clean
A command for finding code that is no longer used and removing it after checking that tests still pass.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
yolo-abort
Immediate halt of /yolo Hive session mid-action — partial state saved, in-flight git operations rolled back where possible, audit log finalized with abort flag.
release
Command "release" from getsentry/toolkit, covering examples, list releases (auto-detect org), list releases in a specific org, view release details and create and finalize a release.