Borrowing it
Nothing to install: this file belongs to devlint/GitWand. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/devlint/GitWand/main/.claude/skills/add-resolver/SKILL.mdgit clone --depth 1 https://github.com/devlint/GitWandWrote 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/skills/devlint/gitwand/add-resolver)<a href="https://agentmods.dev/skills/devlint/gitwand/add-resolver"><img src="https://agentmods.dev/badge/skills/devlint/gitwand/add-resolver/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/skills/devlint/gitwand/add-resolver"><img src="https://agentmods.dev/badge/skills/devlint/gitwand/add-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.01608 |
| Opus 5.5 | $0.00036 | $0.00643 |
| Sonnet 5.5 | $0.00018 | $0.00322 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
add-resolver scanned grade A with 1 finding 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 2mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
browsers — no Node.js imports (`fs`, `path`, `child_process`). If no How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: add-resolver
Guide the agent through adding a format-specific resolver to packages/core
end to end — file creation, dispatcher wiring, tests, and docs — without
missing any of the four required touch points.
Step 1 — Qualify the need
Answer these before writing any code:
- Format / extension? (e.g.
.prisma,composer.lock,.tf,.toml) - Is it a lockfile? If yes → confidence is
0.95by convention. Lockfile conflicts are almost always trivially re-generable, so high confidence is appropriate. - Resolution strategy? Examples:
- Structured config (key = value) → merge non-conflicting keys
- Lockfile → accept one side; file is regenerable
- Source code → be conservative, 0.70–0.80 max
- Browser-compatible parsing available?
packages/coremust run in browsers — no Node.js imports (fs,path,child_process). If no parser lib is available, write a pure string-manipulation parser.
Confidence score guidelines:
| File type | Score |
|---|---|
| Lockfile | 0.95 |
| Structured config (JSON, YAML, TOML, dotenv) | 0.85–0.90 |
| Source code | 0.70–0.80 |
Never exceed 0.95 unless perfectly deterministic |
— |
Step 2 — Create the resolver file
Create packages/core/src/resolvers/<format>.ts. Follow this exact shape,
which mirrors all existing resolvers in the directory:
/**
* GitWand — <FORMAT> resolver
*
* Strategy: [describe the resolution strategy precisely]
*
* Handled cases:
* - [case 1]
* - [case 2]
* - [non-resolvable case → return null]
*/
// ✅ Allowed: pure string manipulation, parsing, algorithms
// ❌ FORBIDDEN: import * as fs from 'fs' / import * as path from 'path'
export interface ResolveResult {
/** Resolved lines, or null if not resolvable */
lines: string[] | null;
/** Human-readable description of what was done (or why it failed) */
reason: string;
}
/**
* Attempts to resolve a <format> conflict.
* Confidence: 0.XX — [justify the score here]
*/
export function tryResolve<Format>Conflict(
baseLines: string[],
oursLines: string[],
theirsLines: string[],
): ResolveResult {
// ... resolution logic ...
return { lines: null, reason: "Non-resolvable: [reason]." };
}
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.
- 2mo ago First seen · 211 lines · 90 tokens per session scan A 8b97ba96657a
add-resolver is a skill published in the GitHub repository devlint/GitWand (194 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,608 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
add-resolver compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| add-resolverdevlint/GitWand | Skill | 194 | yesterday | MIT | A | 90 | Claude Code |
| hunk-launch-videomodem-dev/hunk | Skill | 9.8k | yesterday | MIT | A | 60 | Claude Code, Codex |
| hunk-releasemodem-dev/hunk | Skill | 9.8k | yesterday | MIT | A | 38 | Claude Code, Codex |
| git-macheteVirtusLab/git-machete | Skill | 1.1k | 3d ago | MIT | A | 165 | Claude Code, Codex |
| doris-repo-reviewapache/doris-skills | Skill | 49 | 2d ago | Apache-2.0 | A | 180 | Claude Code, Codex |
| doris-debug-importapache/doris-skills | Skill | 49 | 2d ago | Apache-2.0 | A | 58 | Claude Code, Codex |
| mergeRockyHong/super-bootstrap | Skill | 3 | yesterday | MIT | A | 130 | Claude Code |