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 chrisblattman/claudeblattman --skill donegit clone --depth 1 https://github.com/chrisblattman/claudeblattmanWrote 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/chrisblattman/claudeblattman/done)<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/done"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/done/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/chrisblattman/claudeblattman/done"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/done.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.00046 | $0.00214 |
| Opus 5 | $0.00023 | $0.00107 |
| Sonnet 5 | $0.00009 | $0.00043 |
| Haiku 4.5 | $0.00005 | $0.00021 |
Grade A, and why
done 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 9d 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.
What it actually says
Done
Close the session by capturing where things stand.
Workflow
- Review what changed this session, what was decided, and what comes next.
- Overwrite
./HANDOFF.mdin the current project folder with a snapshot of 30 lines or fewer, using these sections:- Status — where the work stands right now
- Next steps — the first concrete things to do next session
- Key files — the paths that matter, each with a one-line note
- Decisions — choices made this session, and briefly why
- Show the user what you wrote.
Replace the whole file each time — HANDOFF.md is a current-state snapshot, not a log. Do not append dated entries.
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.
- 9d ago First seen · 21 lines · 46 tokens per session scan A 49af93c7f67d
done is a skill published in the GitHub repository chrisblattman/claudeblattman (454 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 214 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-30.
Other skills, from other repositories
skill-extract
Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.
update-focus
Update current-focus.md with a structured session summary. Use when the user asks to update current-focus.md with a structured session summary.
meetings-weekly
Weekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.
meetings-search
Search meeting transcripts and voice memos for people, topics, decisions, commitments, or remembered ideas. Use when the user asks what was discussed, decided, or said across their meeting history. Not for preparing an upcoming meeting; use $meetings-prep.
session-health
Check whether the current session has coherent guidance, focus, handoff state, working-tree ownership, and enough context to proceed safely. Use when starting, resuming, or diagnosing a confused session. Not for auditing the machine or deployed AI infrastructure; use $system-audit.
meetings-cleanup
Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.