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.
curl -O https://raw.githubusercontent.com/saubakirov/trace-first-starter/master/.claude/commands/tfw-handoff.mdgit clone --depth 1 https://github.com/saubakirov/trace-first-starterWrote 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.
[](https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-handoff)<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-handoff"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-handoff/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.
<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-handoff"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00011 | $0.03173 |
| Opus 5 | $0.00005 | $0.01587 |
| Sonnet 5 | $0.00002 | $0.00635 |
| Haiku 4.5 | $0.00001 | $0.00317 |
Grade A, and why
tfw-handoff 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TFW Handoff — Task Execution by New Agent
Roles: Coordinator (hands off) → Executor (receives, questions, implements) Input: Approved HL + TS files Output: RF file with implementation results
🔒 ROLE LOCK: EXECUTOR Permitted artifacts: ONB, RF. Forbidden actions: writing HL, writing TS, writing REVIEW, modifying HL, changing scope. The executor MUST NOT modify HL or TS. If scope issues are found — write them in ONB and STOP.
Read Contract
Root instructions are already active. Read this workflow completely, then select inputs in this order. Every shared range is addressed by its unique Markdown heading.
| Order | Input | Checkpoint purpose | Authority |
|---|---|---|---|
| 1 | selected phase/task status.md and journal/ |
current state, authority, and lineage before all other material | task-local |
| 2 | master HL, phase HL when present, and the highest approved TS lineage | frozen purpose, phase derivation, and one governing order | governing task artifacts |
| 3 | prior REVIEW only on a returned REVISE; then artifacts referenced by the governing TS | round basis and declared inputs | governing task artifacts |
| 4 | .tfw/project_config.yaml → tfw.scope_budgets |
VALUE decomposition triggers and delegated-authority multiplier | project configuration |
| 5 | .tfw/conventions.md headings Task control files, Session identity, Artifact file naming, Task Statuses, Safety and Execution Honesty, and Anti-patterns (prohibited) |
state/event writes, identity, revisions, lifecycle, evidence honesty, prohibitions | shared rule |
| 6 | HL §7.2 citations, then relevant implementation files named by the TS | inherited decision context and implementation facts | named source |
| 7 | .tfw/templates/ONB.md, .tfw/templates/evidence/EV.md, and .tfw/templates/RF.md, each only at its gate |
output form | template |
Do not reload AGENTS.md or full conventions.md, glossary.md, or KNOWLEDGE.md. On a revision
return, add the highest TS, prior REVIEW, and lineage range; do not reread unchanged HL, state, or
shared authority in the same session. Missing or duplicate addressed headings are a hard stop under
conventions.md → Context Selection.
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.
- yesterday Changed · +19 lines 46d25df855fa
- 4d ago Changed · +15 lines 84423d32308c
- 9d ago First seen · 189 lines · 11 tokens per session scan A 4d94c59d0b4d
tfw-handoff is a command published in the GitHub repository saubakirov/trace-first-starter (29 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 3,173 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.
Other commands, from other repositories
fw-setup-use
Workspace FDK stack switch — nvm use from .nvmrc or explicit 10/9 (Node 24.11 vs 18); optional --write-nvmrc and --global flags.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.
fw-setup-status
Check FDK and Node.js installation status (/fw-setup status); optional --verbose diagnostics.
openehr-explain
One-stop router that explains or looks up any openEHR thing — auto-detects an archetype, a template, an RM/AM/BASE type, an RM structural concept, an ADL idiom, an AQL query or keyword, or a terminology code (replaces /archetype-explain, /template-explain, /type-spec, /rm-structure, /adl-idiom, /terminology).
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
swarm-init
Initialize a Ruflo swarm with specified topology and configuration.