Borrowing it
Nothing to install: this file belongs to ScientiaCapital/unsloth-mcp-server. 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/ScientiaCapital/unsloth-mcp-server/main/.claude/commands/done.mdgit clone --depth 1 https://github.com/ScientiaCapital/unsloth-mcp-serverWrote 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/scientiacapital/unsloth-mcp-server/done)<a href="https://agentmods.dev/commands/scientiacapital/unsloth-mcp-server/done"><img src="https://agentmods.dev/badge/commands/scientiacapital/unsloth-mcp-server/done.svg" alt="Measured on agentmods" 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.00011 | $0.00280 |
| Opus 5 | $0.00005 | $0.00140 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 7d 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 — End of Day
Instructions
-
Check git state:
git status --short git log --oneline -5 -
If dirty files exist:
- Show what's uncommitted
- Ask: "Want me to /ship these or discard?"
-
Quick security check (5 seconds, not a full sweep):
grep -r "sk-\|AKIA\|ghp_" --include="*.ts" --include="*.py" --include="*.env" . 2>/dev/null | grep -v node_modules | grep -v .git | head -5 -
Report:
## End of Day: PROJECT_NAME | Check | Status | |-------|--------| | Dirty files | 0 (or list them) | | Last commit | message + age | | Secrets scan | clean | Done. See you tomorrow.
If everything is clean, just say "All clean. Done for today."
No observer reports. No portfolio metrics. No 6-phase ceremony. Those are for /end on big feature days.
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.
- 7d ago First seen · 45 lines · 11 tokens per session scan A 461bfac44291
done is a command published in the GitHub repository ScientiaCapital/unsloth-mcp-server (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 280 once invoked, about $0.0001 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.