ai-code-graph: Command for Claude Code

.claude/commands/tm/to-done.md

to-done is a command for Claude Code from sakrut/ai-code-graph. It costs 0 tokens per session (216 once invoked), scanned A, a copy of to-done, MIT.

A task-management command that marks a task as completed after checking its requirements and project state.

In plain words
What is it for?
Use it to finish a task, update dependent work and sprint progress, record implementation notes, and show tasks that are now available.
Why use it?
It helps ensure that acceptance criteria, subtasks, testing, and code commits are handled before the task is closed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is sakrut/ai-code-graph's own configuration. It tells Claude Code how to work on ai-code-graph itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-code-graph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sakrut/ai-code-graph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sakrut/ai-code-graph/main/.claude/commands/tm/to-done.md
Clone the repo
git clone --depth 1 https://github.com/sakrut/ai-code-graph

Made for: Claude Code.

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

agentmods badge for to-done

README.md
[![agentmods](https://agentmods.dev/badge/commands/sakrut/ai-code-graph/to-done/github.svg)](https://agentmods.dev/commands/sakrut/ai-code-graph/to-done)
Your own site
<a href="https://agentmods.dev/commands/sakrut/ai-code-graph/to-done"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/to-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.

agentmods 80×15 button for to-done

Your own site · 80×15
<a href="https://agentmods.dev/commands/sakrut/ai-code-graph/to-done"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/to-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 216 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.1 $0.00000 $0.00216
Opus 5.5 $0.00000 $0.00086
Sonnet 5.5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00022

Measured 1mo ago against content hash dad1cbe83668, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

88% identical to to-done — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/tm/to-done.md · 47 lines

What it actually says

To Done

Arguments: $ARGUMENTS Mark a task as completed.

Arguments: $ARGUMENTS (task ID)

Completing a Task

This command validates task completion and updates project state intelligently.

Pre-Completion Checks

  1. Verify test strategy was followed
  2. Check if all subtasks are complete
  3. Validate acceptance criteria met
  4. Ensure code is committed

Execution

task-master set-status --id=$ARGUMENTS --status=done

Post-Completion Actions

  1. Update Dependencies

    • Identify newly unblocked tasks
    • Update sprint progress
    • Recalculate project timeline
  2. Documentation

    • Generate completion summary
    • Update CLAUDE.md with learnings
    • Log implementation approach
  3. Next Steps

    • Show newly available tasks
    • Suggest logical next task
    • Update velocity metrics

Celebration & Learning

  • Show impact of completion
  • Display unblocked work
  • Recognize achievement
  • Capture lessons learned
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. 1mo ago First seen · 47 lines · 0 tokens per session scan A dad1cbe83668

Subscribe to this mod's changes

to-done is a command published in the GitHub repository sakrut/ai-code-graph (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 216 tokens. A static security scan graded it A with 0 findings. It is 88% identical to to-done, differing in 3 lines, and is treated as a copy.