trace-first-starter: Command for Claude Code

.claude/commands/tfw-resume.md

tfw-resume is a command for Claude Code from saubakirov/trace-first-starter. It costs 13 tokens per session (977 once invoked), scanned A, original, MIT.

A command that resumes a multi-phase task by reading its existing records and producing a status summary with a recommendation for the next phase.

In plain words
What is it for?
Use it at the beginning of a new or returning session to check phase progress, verify the required context, and decide what should happen next.
Why use it?
It helps a coordinator continue work after a pause without repeating completed steps or starting execution prematurely.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

Nothing to install: this file belongs to saubakirov/trace-first-starter. 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/saubakirov/trace-first-starter/master/.claude/commands/tfw-resume.md
Clone the repo
git clone --depth 1 https://github.com/saubakirov/trace-first-starter

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 tfw-resume

README.md
[![agentmods](https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-resume/github.svg)](https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-resume)
Your own site
<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-resume"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-resume/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 tfw-resume

Your own site · 80×15
<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-resume"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 977 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.00013 $0.00977
Opus 5 $0.00006 $0.00489
Sonnet 5 $0.00003 $0.00195
Haiku 4.5 $0.00001 $0.00098

Measured today against content hash db547cf4ef2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

tfw-resume 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 today.

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/tfw-resume.md · 78 lines

How it starts

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

TFW Resume — Selected Work and Phase Status

Role: Coordinator (new or returning) Output: Selected closing/recovery result, or phase status matrix and recommendation

🔒 ROLE LOCK: COORDINATOR Permitted: selected Coordinator closing/control records and separately attributed REVIEW closing entries; read-only status analysis, then Phase HL/TS only after the user selects planning. Forbidden: execution, ONB, RF, RES, REVIEW creation/proposals, and code changes.

Read Contract

Read this workflow completely, then select inputs in order; shared ranges use unique headings.

Order Input Checkpoint purpose Authority
1 named task/phase state; else .tfw/project_config.yamltfw.task_containers only to resolve it, then status.md/journal/ state first task/config
2 each current phase's own status.md and journal/ for unselected next-phase work when the task is PHASES; an explicitly selected phase uses its own state phase truth without task-level rollup phase-local
3 referenced authority/lineage; master HL/TS only if named governing purpose/scope/artifact governing artifacts
4 highest completed/returned REVIEW; RF only for claim detail verdict/disposition/return governing artifacts
5 .tfw/conventions.md headings Task control files, Session identity, Artifact file naming, Task Statuses, and The 🔄 REVISE route identity/state/route shared rule
6 for selected closing/recovery: .tfw/conventions.md heading Closing and record recovery; only referenced acceptance, evidence and actual final effects selected close or reconstructable carrier repair shared rule/governing artifacts

Indexes/globs/chat/unrelated RF/full libraries are not state; heading/lineage defects stop under Context Selection.

Who Is Acting

Before writing resolve handle: one profile, valid binding, or one question. Never infer; events use human on_behalf_of and tool via.

Read the full file on GitHub · 78 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. today Changed · +9 lines · -1 tokens per session db547cf4ef2e
  2. 2d ago Changed · -40 lines e65fc0229f8e
  3. 6d ago Changed · -5 lines b1d8c69e523a
  4. 10d ago First seen · 114 lines · 14 tokens per session scan A 93e073f4da4a

Subscribe to this mod's changes

tfw-resume is a command published in the GitHub repository saubakirov/trace-first-starter (29 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 977 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.