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/releasenpx skills add devlint/GitWand --skill releasegit 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.00064 | $0.02013 |
| Opus 5 | $0.00032 | $0.01007 |
| Sonnet 5 | $0.00013 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
release 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release — Guide étape par étape
Étape 0 — Identifier le scope
Demander à l'utilisateur quel scope releaser (sauf si le contexte est évident) :
| Scope | Ce qui est publié | Tag git |
|---|---|---|
| monorepo (défaut) | Tout : desktop + npm packages | vX.Y.Z |
| vscode | Extension VS Code uniquement | Versioning indépendant |
Si l'utilisateur dit "je veux bumper la version", "nouvelle release", "publier le CLI", etc. → scope monorepo par défaut.
Étape 1 — Vérifications pré-release
Exécuter dans l'ordre, stopper si l'une échoue :
# 1. Pas de changements non commités
git status
# 2. Sur main (ou branche de release)
git branch --show-current
# 3. À jour avec le remote
git fetch origin && git log origin/main..HEAD --oneline
# 4. Tests passent
pnpm test
# 5. Build réussit
pnpm build
Bloquer et signaler si une vérification échoue avant de continuer.
Étape 2 — Mettre à jour CHANGELOG.md (racine)
Ouvrir CHANGELOG.md (racine du repo) et :
- Renommer
## [Unreleased]en## [X.Y.Z] - YYYY-MM-DD - Ajouter une nouvelle section
## [Unreleased]vide au-dessus - Vérifier que toutes les features/fixes depuis la dernière release sont documentés
- Ajouter le lien de comparaison en bas du fichier :
[X.Y.Z]: https://github.com/devlint/GitWand/releases/tag/vX.Y.Z
Format attendu (Keep a Changelog) :
## [Unreleased]
## [2.4.0] - 2026-04-28
### Added
- Support for .prisma resolver
### Fixed
- Context line detection bug in diff parser
Étape 2b — Mettre à jour roadmap.md
Ouvrir roadmap.md et :
- Déplacer les items livrés dans cette release depuis leur section actuelle (In Progress / Planned) vers le bloc Shipped correspondant à la version.
- Si des follow-ups ou limitations ont été identifiés pendant le dev, les ajouter dans la section planifiée appropriée.
Étape 2c — Mettre à jour website/changelog.md
website/changelog.md est le miroir éditorial public — format narratif (prose
et sections thématiques), pas le format Keep a Changelog. Il doit couvrir tout
l'historique depuis v0.0.1.
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 · 208 lines · 64 tokens per session scan A 4df09235eccd
release is a skill published in the GitHub repository devlint/GitWand (167 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 2,013 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 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…