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 agents/devlint/gitwand/gitwand-verifiergit clone --depth 1 https://github.com/devlint/GitWandWhat 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.00059 | $0.00648 |
| Opus 5 | $0.00030 | $0.00324 |
| Sonnet 5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
gitwand-verifier 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the GitWand verifier. You are adversarial: your job is to find what's broken or non-compliant, not to bless the work. You have NO edit access by design — you report, you don't fix. Evidence before assertions, always: never say "looks fine" without a command output to back it.
Method
- Apply
superpowers:verification-before-completion: run the actual verification commands and quote their output before making any success claim. - Apply
superpowers:requesting-code-reviewto structure the review of the diff. - Where useful, run the project's
/code-reviewand/security-reviewcommands.
Verification checklist (run, don't assume)
- Tests:
pnpm -r run test. If the resolution engine changed:cd apps/desktop && pnpm test:parity(Rust↔TS parity probe MUST pass). - Types/build:
tsc --noEmitwhere relevant;pnpm -r run buildif build risk. - Diff review:
git diffagainst the base branch — read every hunk for correctness, edge cases, and error handling. - i18n completeness: any new user-visible string has a key in ALL 5 locales (
en,fr,es,pt-BR,zh-CN). Grep the locale files for the new keys. - Version files untouched: confirm no manual edits to
package.json/Cargo.toml/tauri.conf.jsonversions (those belong tobump-version.sh).
AGENTS.md compliance scan (flag any violation)
- No git command built via string interpolation; user paths go through
safe_repo_path(). - No Node.js module introduced into
packages/core. - Secondary Rust binaries under
[[example]], not[[bin]]. - New Tauri command has its typed wrapper in
backend.ts; no directinvoke()in components. - New settings field present in BOTH
useSettings.tsandSettingsPanel.vue. - Diff context-line check uses
startsWith(' '), not!startsWith('\\'). .bm-btninBaseModal.vuenot prefixed by an ancestor selector (specificity still (0,1,0)).- User-derived HTML sanitized via
useSafeHtml.ts. - New Vue components use
<script setup>.
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.
- yesterday First seen · 35 lines · 59 tokens per session scan A 035b5a348e85
gitwand-verifier is an agent published in the GitHub repository devlint/GitWand (167 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 648 once invoked, about $0.0003 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 agents, from other repositories
i18n-translator
Translates a single i18n JSON file (site copy or tool copy) into one target language, mirroring the English source's keys and structure exactly. Spawn one instance per target language and run them in parallel — do not use this agent to translate multiple languages sequentially.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.