Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/saubakirov/trace-first-starter/tfw-initgit 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-init)<a href="https://agentmods.dev/commands/saubakirov/trace-first-starter/tfw-init"><img src="https://agentmods.dev/badge/commands/saubakirov/trace-first-starter/tfw-init.svg" alt="Measured on agentmods" 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.00016 | $0.03452 |
| Opus 5 | $0.00008 | $0.01726 |
| Sonnet 5 | $0.00003 | $0.00690 |
| Haiku 4.5 | $0.00002 | $0.00345 |
Grade A, and why
tfw-init 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TFW Init — Project Initialization
Role: Coordinator Output: Configured TFW project with its first task created in the container When to use: Once, when adding TFW to a project for the first time
🔒 ROLE LOCK: COORDINATOR Permitted: creating project files (CONFIG, AGENTS.md, README route, task container, adapter), calling /tfw-research, writing RES/RF for the first task. Forbidden: writing code unrelated to TFW setup.
Phase 0: Detect Full Init vs Adapter Attach/Repair
Before the tutorial question or project discovery, inspect the filesystem.
- Full init:
.tfw/is newly copied and the project has no configured task container or TFW task traces. Continue with Phases 1-5. - Existing TFW project:
.tfw/exists,tfw.task_containersis configured, and the container contains TFW traces. Preserve all project state. Do not repeat discovery, interview, research, config creation, or the init task.
For an existing TFW project, ask which missing or broken tool adapter should be attached only if the current tool cannot be inferred. For Codex:
- Read
.tfw/adapters/codex/README.mdcompletely. - Run its idempotent Install or Repair procedure.
- Preserve
project_config.yaml,knowledge_state.yaml, project docs, task state and journals, task traces, and all rootAGENTS.mdcontent outside the managed TFW markers. - Verify the installed skill copies, managed routing block, legacy duplicate cleanup,
and literal
/tfw-*routing as the adapter README requires. - Report what was repaired and stop. Adapter attach/repair does not create another first task or rewrite project knowledge.
Tutorial Mode
At the start, ask the user: "Is this your first time using TFW? I can explain each step as we go." If yes — add brief explanations at each phase. If no — proceed efficiently, skip explanations.
If tutorial mode, suggest:
"We recommend reading .tfw/README.md — it explains the philosophy behind TFW
and takes about 5 minutes. Everything else in the repo is designed for AI agents,
not for you to read line by line."
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 · -1 lines 0344575b32ea
- 5d ago First seen · 272 lines · 16 tokens per session scan A 8e1d39b5049f
tfw-init is a command published in the GitHub repository saubakirov/trace-first-starter (29 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 3,452 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.