tachi: Command for Claude Code

.claude/commands/continue.md

continue is a command for Claude Code from davidmatousek/tachi. It costs 10 tokens per session (613 once invoked), scanned A, original, Apache-2.0.

A session handoff command that records the current Git work and saves it in a NEXT-SESSION.md file. It also notes which development stage is next.

In plain words
What is it for?
Use it before ending a coding session or handing work to someone else. It helps continue feature work from specification through planning, task tracking, and implementation.
Why use it?
It prevents important context from being lost when work moves to another session. The next person or session can see the branch state, recent commits, unfinished tasks, and next action.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is davidmatousek/tachi's own configuration. It tells Claude Code how to work on tachi 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 tachi configures →

Reuse

Borrowing it

Nothing to install: this file belongs to davidmatousek/tachi. 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/davidmatousek/tachi/main/.claude/commands/continue.md
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/tachi

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 continue

README.md
[![agentmods](https://agentmods.dev/badge/commands/davidmatousek/tachi/continue/github.svg)](https://agentmods.dev/commands/davidmatousek/tachi/continue)
Your own site
<a href="https://agentmods.dev/commands/davidmatousek/tachi/continue"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/continue/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 continue

Your own site · 80×15
<a href="https://agentmods.dev/commands/davidmatousek/tachi/continue"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/continue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 613 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 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.1 $0.00010 $0.00613
Opus 5.5 $0.00004 $0.00245
Sonnet 5.5 $0.00002 $0.00123
Haiku 4.5 $0.00001 $0.00061

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

Security

Grade A, and why

continue 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

Copies of this mod

1 near-identical copy found in the catalogue:

  • continue — 100% identical, 0 lines differ
.claude/commands/continue.md · 93 lines

How it starts

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

Purpose

Capture current work context and generate NEXT-SESSION.md for seamless session handoff.

File Location

Branch Pattern Output Location
NNN-* (feature branch) specs/NNN-*/NEXT-SESSION.md
Other branches docs/prompts/NEXT-SESSION.md

Context to Capture

Run these git commands (in parallel):

  • git branch --show-current - current branch
  • git status --porcelain - uncommitted changes
  • git log -1 --format='%h %s' - last commit
  • git log --oneline -5 - recent work

If on feature branch, also check:

  • Which spec files exist (spec.md, plan.md, tasks.md)
  • Task progress from tasks.md: count [x] (done) vs [ ] (pending)

Phase Detection

Files Present Phase Next Action
No spec.md specify Run /aod.spec
No plan.md plan Run /aod.project-plan
No tasks.md tasks Run /aod.tasks
All present implement Next pending task from tasks.md

Output Template

# Session Continuation: {Feature Name}

**Generated**: {YYYY-MM-DD HH:MM}
**Branch**: {branch}
**Last Commit**: {hash} {message}

## Completed This Session

{List recent commits from git log}

## Current State

- **Phase**: {specify|plan|tasks|implement}
- **Uncommitted**: {file count} files ({list} or "Clean - all committed")
- **Tasks**: {X}/{Y} complete (if tasks.md exists)

## Next Actions

1. {Immediate next step based on phase}
2. {Following step}

## Context Files

{List relevant files based on phase and changes}

## Resume Command

\`\`\`bash
claude "Resume {feature} (branch: {branch}). Last: {commit summary}. Next: {action}."
\`\`\`

User Output

After writing NEXT-SESSION.md, report:

✓ Session file created: {path}

Current: {branch} | Phase: {phase} | {X} uncommitted files
Tasks: {completed}/{total} (if applicable)

Resume next session:
  claude "Resume {feature}. Last: {summary}. Next: {action}."

Error Handling

Scenario Action
Not a git repo ERROR: "Must be run from within a git repository"
Spec dir not found Fall back to docs/prompts/NEXT-SESSION.md
Git commands fail Report specific error

Read the full file on GitHub · 93 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. 1mo ago First seen · 93 lines · 10 tokens per session scan A 061e1a6f4b02

Subscribe to this mod's changes

continue is a command published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 613 once invoked, about $0.0000 per session on Opus 5.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.