Borrowing it
Nothing to install: this file belongs to fo0/clawstash. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fo0/clawstash/main/.claude/skills/done/SKILL.mdgit clone --depth 1 https://github.com/fo0/clawstashWrote 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/fo0/clawstash/done)<a href="https://agentmods.dev/skills/fo0/clawstash/done"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/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/fo0/clawstash/done"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/done.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.00072 | $0.01615 |
| Opus 5.5 | $0.00029 | $0.00646 |
| Sonnet 5.5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
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 26d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Done — Work Closure
When to Use
- User says "done", "fertig", "finished", "abschluss", "/done"
- End of a feature, bugfix, or task when ready to wrap up
Scope Boundaries
Owns: closing a piece of work out — format, the automated-check chain, scope check, commit, push, closing the issue of work that landed without a PR.
Does not own: the review itself (basic-review), the PR object (pr), remote build state (ci). It suggests those and never runs them — that fence is what keeps /done predictable enough to type without reading it first.
Workflow
1. Detect branch context
git rev-parse --abbrev-ref HEAD && git status --porcelain && git log origin/$(git rev-parse --abbrev-ref HEAD)..HEAD --oneline 2>/dev/null || echo "no upstream"
Classify:
main/master/develop/trunk→ main branch mode (conservative)- anything else → feature branch mode (standard)
2. Read CLAUDE.md closure requirements
- Commands section → identify the automated-check commands, in the canonical order stated there
- Git Conventions → commit format (e.g. Conventional Commits), branch rules, merge strategy
- Documentation Rules → verify affected docs (CLAUDE.md, README.md, MEMORY.md, SCRATCHPAD.md, BACKLOG.md) are up to date
3. Auto-format (write mode)
Run this project's format-write command, exactly as CLAUDE.md → Commands names it. It MUST run before the rest of the chain — formatting drift introduced during the session otherwise reaches CI and fails the format check there.
- If no format-write command is listed in CLAUDE.md, skip this step (project has no formatter configured).
- If formatting changed files, stage them with
git add -uso they go into the upcoming commit (step 6) — do NOT split formatting into its own commit. - Re-run
git status --porcelainafter formatting to see what changed.
4. Run automated checks
Execute the project's check chain from CLAUDE.md → Commands, in the order stated there. If any stage fails:
- Feature branch: report failure, stop. Do not commit.
- Main branch: hard stop. Never push to main on red.
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.
- 26d ago Changed · +5 tokens per session 3d4bab975837
- 1mo ago Changed · -8 lines 828eaa459a72
- 1mo ago Changed dd883897630f
- 1mo ago Changed d33bc94e26da
- 1mo ago Changed · +7 lines e3d11a22ff63
- 2mo ago First seen · 109 lines · 67 tokens per session scan A 8dd97b28221f
done is a skill published in the GitHub repository fo0/clawstash (1 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,615 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…