done

A session-ending command that records what happened during a coding session and preserves notes for the next one. It also checks project changes and the current .STATUS file.

In plain words
What is it for?
Summarizing completed work, checking changed files and recent commits, updating project status, and suggesting a commit message.
Why use it?
It helps prevent losing progress, decisions, and the next step when work stops between sessions.

Command

Install

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.

agentmods
npx agentmods add commands/data-wise/claude-plugins/done
Clone the repo
git clone --depth 1 https://github.com/Data-Wise/claude-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03393
Opus 5 $0.00000 $0.01697
Sonnet 5 $0.00000 $0.00679
Haiku 4.5 $0.00000 $0.00339

Measured yesterday against content hash 6322fba2ad47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

workflow/commands/done.md · 573 lines

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:

  1. 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
    
  2. Files modified

    git diff --name-status 2>/dev/null
    git diff --cached --name-status 2>/dev/null
    
  3. 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:

  1. CLAUDE.md staleness (features added but not documented)
  2. Orphaned docs (files not linked in mkdocs.yml or README)
  3. README/docs divergence (inconsistent content)
  4. Missing CHANGELOG entries (undocumented commits)

Read the full file on GitHub · 573 lines

Changes

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.

  1. yesterday First seen · 573 lines · 0 tokens per session scan A 6322fba2ad47

Subscribe to this mod's changes

done is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d 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.