A workflow for upgrading a project's TFW files from a named upstream Git version. Git is a tool for tracking code changes, and upstream means the source project being followed.

Use it when an operator needs to update the project's .tfw configuration and workflows from a tagged or explicitly chosen Git revision.

It helps apply a specific framework release while checking that the selected version, rather than a moving development branch, is used.

How saubakirov/trace-first-starter configures Claude Code

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-update/github.svg)](https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-update)

Your own site

<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-update"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-update/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-update"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-update.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 2,828 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.02828
Opus 5.5	$0.00004	$0.01131
Sonnet 5.5	$0.00002	$0.00566
Haiku 4.5	$0.00001	$0.00283

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

Security

Grade A, and why

tfw-update 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 18d 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.

.claude/commands/tfw-update.md · 188 lines

How it starts

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

TFW Update — Framework Upgrade Workflow

🔒 ROLE LOCK: COORDINATOR. Apply only authorized framework/config/adapter migrations and one project-owned receipt. Never perform project implementation, task lifecycle work, new external effects, or writes before source/authority gates resolve.

Read Contract

Root instructions are active. Until a target is pinned, this installed workflow is the only update contract; afterward the pinned target's update.md governs.

Order	Input	Checkpoint purpose	Authority
1	selected task/phase `status.md`, `journal/`, when task-bound	routing and lineage	task-local
2	`.tfw/project_config.yaml` → `tfw.upstream`, installed provenance/project keys; `.tfw/VERSION`; receiver `.tfw/README.md` when present	source, version, receiver purpose	installed project/config
3	operator tag or explicitly authorized immutable commit and its `.tfw/VERSION`	one target	owner/Git object
4	pinned `.tfw/.upstream/.tfw/workflows/update.md`	target algorithm	pinned target
5	intervening pinned CHANGELOG ranges and every named/applicable migration; target migration at equal version/unfinished attempt; `{major}.0.0.md` on a major crossing	migration obligations	pinned history/receiver evidence
6	`.tfw/adapters/manifest.yaml`; briefing and update-receipt templates at their gates	copies and outputs	manifest/templates

Never read live source HEAD, unpinned target files, full changelog/common libraries or project-state bodies. Missing/incoherent target workflow, range or required guide stops.

Step 0 — Activation and pin

Apply root activation/routing before pinning or writing; require exact owner-direct /tfw-update and, when task-bound, the actual Coordinator. Preserve legacy statuses. Add a complete routing spine only when accountable authority supplies all five exact values; otherwise report the missing decision. For a complete five-field carrier, preserve its actual baseline/native-gates choice and add the paired reporting/selection_ref only after verifying the human source and immutable ceiling. Partial original/new forms refuse; do not infer a new delegation, dialogue or owner-transfer.

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

18d ago Changed · +10 lines e684a3e065a4
21d ago Changed · +34 lines 0635dcc92dfa
22d ago Changed · +17 lines 3042de854a56
27d ago Changed · +4 lines dbd57261dc81
28d ago Changed · -157 lines · -4 tokens per session 033c599388fa
1mo ago Changed · +17 lines 474491f4b930
1mo ago Changed · +17 lines 677f98c2ba61
1mo ago Changed · +105 lines · +1 tokens per session 0fe991ac0b29
1mo ago Changed · -17 lines b9edd9841094
1mo ago First seen · 158 lines · 13 tokens per session scan A deab790b6612

Subscribe to this mod's changes

tfw-update is a command published in the GitHub repository saubakirov/trace-first-starter (30 stars, last pushed 9d ago), licensed MIT. It adds 10 tokens to every session and 2,828 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.

Git and workflow agentic-ai ai knowledge-management product-engineering skills

trace-first-starter: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

TFW Update — Framework Upgrade Workflow

Read Contract

Step 0 — Activation and pin

What this file has done since we first saw it

Other commands, from other repositories

github-swarm

release

pr-enhance

project

commit-push-pr

devkit.github.review-pr