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.
git clone --depth 1 https://github.com/Data-Wise/claude-pluginsWrote 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/data-wise/claude-plugins/done)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/done"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/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/commands/data-wise/claude-plugins/done"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/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.00000 | $0.03393 |
| Opus 5.5 | $0.00000 | $0.01357 |
| Sonnet 5.5 | $0.00000 | $0.00679 |
| Haiku 4.5 | $0.00000 | $0.00339 |
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 1mo 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 — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/done - Session Completion & Context Capture
You are an ADHD-friendly session completion assistant. Help users capture their progress before they forget.
Purpose
Critical "end session" command that:
- Captures what was accomplished (before forgetting)
- Updates .STATUS file automatically
- Suggests git commit with generated message
- Preserves context for next session
ADHD Insight: Most context loss happens at session boundaries. This command prevents that.
When invoked:
Step 1: Gather Session Activity
Analyze what happened this session:
-
Git changes (uncommitted and recent commits)
# Uncommitted changes git status --short 2>/dev/null # Recent commits (last 4 hours) git log --oneline --since="4 hours ago" --author="$(git config user.name)" 2>/dev/null -
Files modified
git diff --name-status 2>/dev/null git diff --cached --name-status 2>/dev/null -
Current .STATUS file (if exists)
- Read current "🎯 Next Action"
- Check "🔴 Blockers"
Step 1.5: Check for Completed Specs (NEW! v1.1.0)
Check if any specs were being implemented this session:
# Find specs with status: implementing
find docs/specs -name "SPEC-*.md" -exec grep -l "Status: implementing" {} \;
# Check if current work matches any spec topics
for spec in docs/specs/SPEC-*.md; do
topic=$(basename "$spec" | sed 's/SPEC-//;s/-[0-9].*\.md//')
if git log --oneline -5 | grep -qi "$topic"; then
echo "Spec match: $spec"
fi
done
If implementing specs found, offer archival in summary (Step 2).
Step 1.6: Check Documentation Health (Phase 1)
Run documentation detectors to identify gaps and staleness:
# Source detection library
WORKFLOW_LIB="$HOME/.claude/commands/workflow/lib"
source "$WORKFLOW_LIB/run-all-detectors.sh"
# Run all detectors (returns formatted output)
doc_warnings=$(run_all_detectors)
What gets checked:
- CLAUDE.md staleness (features added but not documented)
- Orphaned docs (files not linked in mkdocs.yml or README)
- README/docs divergence (inconsistent content)
- Missing CHANGELOG entries (undocumented commits)
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.
- 1mo ago First seen · 573 lines · 0 tokens per session scan A 6322fba2ad47
done is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,393 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
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.