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/devlint/gitwand/gitwand-mcpnpx skills add devlint/GitWand --skill gitwand-mcpgit 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.00000 | $0.00574 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
gitwand-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitWand MCP Server
Use GitWand's MCP server to automatically resolve Git merge conflicts from any AI agent (Claude, Claude Code, Cursor, Windsurf, etc.).
Install
npx @gitwand/mcp
Or add to your MCP client config (Claude Desktop, Claude Code, etc.):
{
"mcpServers": {
"gitwand": {
"command": "npx",
"args": ["@gitwand/mcp"]
}
}
}
Tools
| Tool | Description |
|---|---|
gitwand_status |
List conflicted files with complexity scores and auto-resolvability percentages |
gitwand_resolve_conflicts |
Auto-resolve trivial conflicts. Returns DecisionTrace + pendingHunks for complex ones |
gitwand_preview_merge |
Dry-run — assess resolvability without modifying files |
gitwand_explain_hunk |
Explain why a specific hunk is complex (full DecisionTrace) |
gitwand_apply_resolution |
Apply a custom resolution you provide to a specific hunk |
Resources
| URI | Description |
|---|---|
gitwand://repo/conflicts |
Live conflict state — files, counts, and auto-resolvability |
gitwand://repo/policy |
Current .gitwandrc config (merge policies, confidence thresholds) |
gitwand://hunk/{file}/{line} |
Raw ours/theirs/base content + confidence for a specific hunk |
Recommended Workflow
gitwand_preview_merge— check what can be auto-resolved vs. needs attentiongitwand_resolve_conflicts— auto-resolve trivial conflicts (writes files)- For each hunk in
pendingHunks:gitwand_explain_hunk— understand why it's complex (DecisionTrace, ours/theirs/base)- Decide on resolution, then
gitwand_apply_resolutionto write it
Merge Policies
Pass policy to gitwand_resolve_conflicts:
prefer-theirs(default) — take the incoming branch's version when safeprefer-ours— favour the current branchprefer-merge— attempt a three-way mergeprefer-safety— only resolve with very high confidencestrict— resolve only non-overlapping / whitespace-only conflicts
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 · 65 lines · 0 tokens per session scan A 103f15461aa8
gitwand-mcp is a skill published in the GitHub repository devlint/GitWand (167 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 574 tokens. 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
hunk-extensions
Maps the hunkdiff/extension authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk…
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-review
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges. Use when the user has a Hunk session running or wants to review diffs interactively.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
mobile-app
像素级 iPhone 15 Pro 边框, 一屏 app 截图.
git-machete
Use whenever invoking the git machete CLI to organize branch chains, compute fork points, run stacked rebases/merges, or manage GitHub/GitLab PR/MR chains - especially in a repo that already has a .git/machete file. Lists which subcommands modify .git/machete, run rebase/merge, run hooks, or read stdin, so the agent…