A task-completion command that checks finished work, reviews the code, updates project progress, and can extract career-related material such as interview stories or résumé bullets.

Use it after a feature or bug fix to run the six verification gates, review the implementation, mark work complete, and optionally record its career value.

It provides a final review and verification step so unfinished requirements, quality issues, or missing project updates are less likely to be overlooked.

done — Command by DanielPodolsky

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/danielpodolsky/ownyourcode/done

Clone the repo

git clone --depth 1 https://github.com/DanielPodolsky/ownyourcode

Made for: Claude Code.

Per session 18 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,635 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.

Model	Per session	Once invoked
Fable 5	$0.00018	$0.03635
Opus 5	$0.00009	$0.01818
Sonnet 5	$0.00004	$0.00727
Haiku 4.5	$0.00002	$0.00364

Measured yesterday against content hash eab3a9c93e01, 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.

.claude/commands/own/done.md · 520 lines

How it starts

The opening of the file, as written. The whole thing — 520 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/own:done

⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (shift+tab). OwnYourCode commands don't work correctly with plan mode.

Complete a task with gate checks, senior-level code review, and career value extraction.

Overview

This command is run when the user finishes a task or feature. It performs:

Gate Checks — 6 Mentorship Gates verification
Code Review — FAANG-level feedback on their code
Task Completion — Update the dashboard (task done, DoD, phase status)
Interview Story — Extract STAR format story (if career_focus allows)
Resume Bullet — Draft action-impact bullet (if career_focus allows)

Profile-Aware Behavior:

Check .claude/ownyourcode-manifest.json for profile.settings.career_focus
If career_focus = "full-extraction" → Run all phases including 5 and 6
If career_focus = "tips-only" → Skip Phases 5 and 6
If career_focus = "none" → Skip Phases 5 and 6, hide CAREER VALUE in summary

Execution Flow

Phase 1: Identify Completed Work

Question: "What did you just finish?"

Options:
1. A task from my active spec
   Description: Completing planned work

2. A bug fix
   Description: Fixed something that was broken

3. A feature (not specced)
   Description: Built something new

4. A refactor
   Description: Improved existing code

If from active spec, read the dashboard to understand context:

Read ownyourcode/dashboard/dashboard-data.js (window.PROJECT)
Find the active phase (first with status !== "complete") and the relevant task in its tasks[] (match by text/detail, note its id)
Note what they were building and why (the phase spec / design)

Phase 2: Gather Changes

Review what code was written:

# Recent commits
git log --oneline -5

# Files changed
git diff --name-only HEAD~1

# Or if uncommitted
git status

Ask them to point to the key files:

"Which files contain the main implementation?"

Read those files to understand what they built.

Read the full file on GitHub · 520 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.

yesterday First seen · 520 lines · 18 tokens per session scan A eab3a9c93e01

Subscribe to this mod's changes

done is a command published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 3,635 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-30.

Code review Debugging Planning agentic-workflow ai-mentorship ai-pair-programming claude-code learning

done

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/own:done

Overview

Execution Flow

Phase 1: Identify Completed Work

Phase 2: Gather Changes

What this file has done since we first saw it

Other commands, from other repositories

project

version

toh-help

diff-docs

update-workflow

start