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 agentmods add commands/kastheco/claude-plugins/donegit clone --depth 1 https://github.com/kastheco/claude-pluginsWhat 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 | $0.00000 | $0.00396 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 2d 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
/kas:done - Land the Plane
Complete the current session by ensuring all work is committed and pushed.
Workflow
Execute these steps in order:
1. Check Git Status
git status
2. Stage and Commit Code Changes (if any)
If there are unstaged changes:
git add <relevant-files>
git commit -m "<appropriate message>"
3. Push to Remote
git pull --rebase
git push
git status # MUST show "up to date with origin/*"
4. Add PR Comment (if PR exists)
If on feature branch with open PR, add completion comment:
# Check for PR
PR_URL=$(gh pr view --json url -q .url 2>/dev/null)
if [[ -n "$PR_URL" ]]; then
gh pr comment --body "$(cat <<'EOF'
## Session Complete
**Completed:**
{completed_items}
**Quality Gates:** {status}
**All changes pushed to remote.**
EOF
)"
fi
Skip gracefully if no PR exists.
5. Clean Up Git State
git stash clear
git remote prune origin
6. Verify Clean State
git status
Must show branch is up to date with origin.
7. Show Summary
Provide:
- Completed: What was done this session
- Quality gates: Status (passed/skipped/N/A)
- Git state: Confirmation all changes pushed
- Next session prompt: Recommended command to continue work
Rules
- Work is NOT complete until
git pushsucceeds - NEVER stop before pushing - that leaves work stranded locally
- If push fails, resolve and retry until it succeeds
- Only run quality gates if code changes were made
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.
- 2d ago First seen · 79 lines · 0 tokens per session scan A 75d3edaee5ab
done is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 396 tokens. 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
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
智能生成 Git 提交信息并提交.
commit
Create a Conventional Commit with signoff.