Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dwarvesf/dwarves-kitnpx agentmods add commands/dwarvesf/dwarves-kit/wrapWrote 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/commands/dwarvesf/dwarves-kit/wrap)<a href="https://agentmods.dev/commands/dwarvesf/dwarves-kit/wrap"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/wrap/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/commands/dwarvesf/dwarves-kit/wrap"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/wrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00105 | $0.24795 |
| Opus 5.5 | $0.00042 | $0.09918 |
| Sonnet 5.5 | $0.00021 | $0.04959 |
| Haiku 4.5 | $0.00011 | $0.02480 |
Grade A, and why
wrap 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 today.
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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-intro (AGENTS.md "Self-intro" convention): open your first reply with exactly one banner line, [kit:wrap] Land the session after ship: board rows, merges, deploy check, tidy, activity line, retro., then proceed.
You are the session's landing step. The operator just shipped, or is ending the session, and nothing in the kit lands that session on its own: board rows stay unflipped, the operator's own green PRs stay unmerged, a merged-but-undeployed PR goes unnoticed, branches and worktrees pile up, and /kit:retro never runs. Your job is one pass over every repo the session touched, closing out every step below in order.
Scope and triggers
Also tidies branches (not just worktrees), writes the activity line, and calls /kit:retro when a shipped PR merged. Additional trigger phrases: 'wrap this up', 'let's wrap', 'pack this up for the day', 'wrap up, update items status, commit, merge PRs and clean up worktrees and stale branches, then pull the latest'. The distill half is ON by default (wrap.distill = true) and skips only when the operator's own kit.toml sets distill = false (a landing-only setup); the invocation carries the word distill (or the operator asks to distill) to turn it on for one run when the knob is off. The follow-through phase (step 10) is OFF by default (wrap.follow_through = "off") and runs when the invocation carries the word follow, including: 'wrap up and follow through', 'wrap and build the rest'.
When this runs
- After
/kit:shipcompletes, for the repo that just shipped. - At the end of a session, before the operator closes the terminal.
- Whenever the operator asks to land, wrap up, or close out the session.
- Never mid-build: a spec still mid-execute has nothing to land yet.
Prerequisites
- Each named repo (or the current repo, when none is named) is a git repository. A non-repo argument prints a skip line and the rest proceed.
ghis optional. When it is absent or unauthenticated, every branch that is not a plain ancestor of the default branch verdictsunknown: LEAVEandbin/wrap mergerefuses with exit 1; the command still runs the other seven steps and reports the degraded state, it never stops for this reason alone.
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.
- today Changed 4dee2b08cbe5
- 6d ago Changed · +1 lines 605d1507e9d8
- 9d ago Changed e3c1a1560332
- 15d ago Changed a4603556fb15
- 18d ago Changed · +1 lines eed18c54e1cc
- 19d ago Changed · +1 lines 05445c4a3725
- 20d ago Changed 60b566de4056
- 21d ago Changed · +11 lines 844e12fbd9fe
- 22d ago Changed · +1 lines 0ff5696404b6
- 23d ago First seen · 383 lines · 105 tokens per session scan A 29738beb0b52
wrap is a command published in the GitHub repository dwarvesf/dwarves-kit (12 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 24,795 once invoked, about $0.0004 per session on Opus 5.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-09-07.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
release
Prepare and publish spec-driven-steroids through the tag-triggered npm release pipeline.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
ship
Run /ship — see .claude/commands/ship.md for the authoritative spec.
mode
Show or switch the project's conformance mode between Enforced and À la carte, within the set the organization allows.
ship
Run the auditors for every exit condition in scope for the requested ship target (review or release), and on pass run the ship steps the organization declared for that target.