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 skills/vouchdev/vouch/vouch-resolve-issuenpx skills add vouchdev/vouch --skill 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.00021 | $0.00283 |
| Opus 5 | $0.00010 | $0.00142 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
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 · 29 lines · 21 tokens per session scan A a27d6df02715
vouch-resolve-issue is a skill published in the GitHub repository vouchdev/vouch (91 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 283 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 skills, from other repositories
release-openclaw-maintainer
Prepare or verify OpenClaw stable, beta, and extended-stable releases, including backport discovery, changelogs, release notes, publish commands, and artifacts.
openclaw-testing
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
autoreview
Structured Codex, Claude, Amp, Pi, or Kimi code review when explicitly requested.
release-openclaw-ci
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
openclaw-ci-limits
Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning .github/workflows/, docs/ci.md, CI runner labels, matrix max-parallel…
auto-qa
Continuously audit, live-test, and stress-test the current OpenClaw codebase across at least ten independently scoped subsystem lanes; default to 100 independently verified, landed root-cause fixes, maintain an evidence-backed report, and announce each merged pull request immediately. Use for OpenClaw-wide autonomous…