trace-first-starter: Command for Claude Code

.claude/commands/tfw-config.md

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

An interactive configuration workflow that changes project settings and synchronizes their repeated values across listed files and adapters.

In plain words
What is it for?
Use it to edit or audit values in project_config.yaml, review every proposed occurrence, apply approved updates, and verify synchronization.
Why use it?
It reduces inconsistent configuration caused by changing one copy while leaving related workflow or convention files unchanged.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-config.svg)](https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-config)
Your own site
<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-config"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-config.svg" alt="Measured on agentmods" 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 1,133 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.01133
Opus 5 $0.00006 $0.00566
Sonnet 5 $0.00003 $0.00227
Haiku 4.5 $0.00001 $0.00113

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

Security

Grade A, and why

tfw-config 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-config.md · 102 lines

How it starts

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

TFW Config — Config Sync Workflow

Role: Coordinator Output: verified or approved config/range updates and affected adapter copies

🔒 ROLE LOCK: COORDINATOR Permitted: project_config.yaml, registered workflow/convention ranges, and affected adapter copies. Forbidden: code and task artifacts.

Read Contract

Root instructions are already active. Read this workflow completely, then read in order.

Order Input Checkpoint purpose Authority
1 .tfw/project_config.yaml current source values project config
2 this workflow's Config Sync Registry the one set of inline targets canonical workflow
3 only each registered target file and unique Section Header range compare or update inline copies registered source range
4 .tfw/adapters/manifest.yaml only when a changed range has adapter copies affected copy/check destinations tooling metadata

Full conventions/glossary/workflows, unregistered ranges, task artifacts, and unrelated adapters are not inputs. A missing or duplicate heading/row/target, unresolved source, or incomplete adapter map is a hard stop.

Edit Mode

  1. Ask what config key and value should change.
  2. Resolve its config value and every registry row. Values with no inline copy remain config-only.
  3. Present one batch preview with old/new values and exact files/headings.
  4. Wait for approval, then update config and every resolved row atomically.
  5. Sync only affected installed adapters through Adapter Sync; verify and report all results.

Verify Mode

For /tfw-config verify, resolve all config values and every registry target, then report each exact match/mismatch. Write nothing. A mismatch is reported, never silently repaired.

Config Sync Registry

scope_budgets

Config Key Target File Section Header Row Label
scope_budgets.decomposition_trigger_files .tfw/conventions.md Scope Budgets (per Phase) Logical touched VALUE files
scope_budgets.decomposition_trigger_loc .tfw/conventions.md Scope Budgets (per Phase) Touched text LOC
scope_budgets.owner_escalation_multiplier .tfw/conventions.md Decomposition, constraints, and change authority Owner escalation multiplier

Read the full file on GitHub · 102 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 · -46 lines 8f0b9e9b499e
  2. 4d ago Changed · -2 lines 58dd991c3665
  3. 8d ago First seen · 150 lines · 13 tokens per session scan A 864ae21fb5b7

Subscribe to this mod's changes

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