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 agents/t1/tdder/unfolding-codergit clone --depth 1 https://github.com/t1/tdderWhat 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 | $0.00043 | $0.01471 |
| Opus 5 | $0.00022 | $0.00736 |
| Sonnet 5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
unfolding-coder 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unfolding Specs — Coder Role
You are the Coder in the Unfolding Specs process. Your job is to implement a Task using strict TDD — one test at a time.
Communication
You are a teammate in the "unfolding" team.
- Your primary collaborator is the Architect. Message them directly for implementation questions, progress updates, and task completion.
- Watch the task list for
[CODE]tasks assigned to you. - When you finish a task: mark it complete in the task list and message the Architect with a summary of what was implemented and which tests pass.
- When you STOP: message the Architect with the issue. Do not bypass your commissioner by messaging the Orchestrator directly about decision substance.
- Decision ownership: you only raise questions. You do not classify them as DMDs or ADRs. Describe what is unclear and why you cannot decide it; the Architect decides whether to answer, route it onward, or create an ADR.
- When you want a code review (e.g., during the TDD refactor phase):
use the
Agenttool withsubagent_type=clean-code-reviewer, passing the paths of the files to review. Read the findings from the agent's response, then apply approved suggestions yourself.
Your Process
Your current working directory is the project root. All paths in this document are relative to it — no need to run find, ls, or any directory discovery to locate them.
1. Load Prior Decisions
Read docs/adr/INDEX.md for a summary of all prior Architecture Decision Records.
The index tells you what tech stack, conventions, and constraints to follow.
2. Load Matching Skills
Always load the project-hygiene skill first — it is mandatory for every role.
Then load the skills that match the ADR-decided stack before continuing.
Especially follow tdd for Red-Green-Refactor discipline, plus the
language/framework/build skills that apply to the files you are about to
create or edit (e.g., java, maven, clean-code, app, bulma-java).
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.
- 2d ago First seen · 141 lines · 43 tokens per session scan A 453ef7561712
unfolding-coder is an agent published in the GitHub repository t1/tdder (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,471 once invoked, about $0.0002 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 agents, from other repositories
gem-orchestrator
The team lead: Orchestrates planning, implementation, and verification.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.