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 skills add redhuntlabs/wizard --skill wrapping-up-a-piecegit clone --depth 1 https://github.com/redhuntlabs/wizardWrote 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/redhuntlabs/wizard/wrapping-up-a-piece)<a href="https://agentmods.dev/skills/redhuntlabs/wizard/wrapping-up-a-piece"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/wrapping-up-a-piece/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/redhuntlabs/wizard/wrapping-up-a-piece"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/wrapping-up-a-piece.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.00032 | $0.01020 |
| Opus 5 | $0.00016 | $0.00510 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
wrapping-up-a-piece 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrapping Up a Piece
What this does
Runs a structured closing pass on a piece of work: handoff, archive, follow-up. Distinct from verifying-before-shipping (which is "is this done?"). This is "now that it's done, what closes it for good?"
When to use
- A project, milestone, or task has reached "done" status
- You're handing off work to someone else
- You're closing out before time off or a context switch
- You want to prevent the work from boomeranging back
What you bring (Inputs)
- The finished piece of work
- Who else is affected (handoff target, downstream consumers, future-you)
- Whether anything was deferred from this piece
What you get (Output)
A clean closure: handoff message sent, artifacts archived, deferrals captured, retrospective if warranted.
How it works (Steps)
This is a workflow.
Stages
Stage 1: Handoff
Identify who needs the work next (or who needs to know it's done). Send them: a one-line summary, a link to the artifact, a one-line "what they should know" note.
Stage 2: Archive
Put the artifact where future-you (or future-them) will find it. Include a one-paragraph context note: why the work happened, what it solved, who decided what.
Stage 3: Capture deferrals
What did you cut from scope, push to next time, or punt? Write each as a ticket / todo / note with enough context that someone (or you in 3 months) could pick it up cold.
Stage 4: Retrospective (if warranted)
For pieces over 1 week of work, write 3 lines: what went well, what didn't, what you'd do differently. Even just for yourself.
Stage 5: Tell the world (optionally)
If someone external benefits from knowing this is done (a customer, a partner, a stakeholder), send the message. Brief, references the artifact, names what changes for them.
Stage 6: Close the file
Mark the ticket / project / doc closed. Resist re-opening for "one more thing" — that goes in deferrals.
Checkpoints
- After Stage 1: handoff sent (or explicitly "no handoff needed")
- After Stage 2: artifact has a context note (not just a file link)
- After Stage 3: every deferral is captured somewhere retrievable
- After Stage 4: retro written for substantial pieces
- After Stage 5: external comms sent (if applicable)
- After Stage 6: project state changed to closed
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.
- 10d ago First seen · 105 lines · 32 tokens per session scan A 1d425ff63f03
wrapping-up-a-piece is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,020 once invoked, about $0.0002 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-31.
Other skills, from other repositories
fzf
A command-line tool for finding items by typing partial text, with results updating as you type. It can search files, shell command history, processes, directories, Git branches, commits, and other text output.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.
screen-detox
A habit-change framework for reducing non-work screen use such as social media, short videos, games, and endless scrolling.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
monkey-mind-meditation
A meditation and reflection guide for a busy or anxious mind. It treats recurring thoughts as something to observe and examine, while noting that acute serious mental-health problems need professional care.
slackcli
Read, send, search, and manage Slack workspaces with the slackcli binary. Installs slackcli if missing and checks or proposes authentication first. Use whenever the user mentions Slack or pastes a slack.com link.