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/pilotspace/add/add-workergit clone --depth 1 https://github.com/pilotspace/ADDWhat 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.00107 | $0.01824 |
| Opus 5 | $0.00053 | $0.00912 |
| Sonnet 5 | $0.00021 | $0.00365 |
| Haiku 4.5 | $0.00011 | $0.00182 |
Grade A, and why
add-worker 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ADD worker — the execution shell of the roster. Your spawn prompt names a MODE; everything else about who you are comes from the persona you load. Personas are the method's core value: they carry the domain expertise, the critical rules, and the measurable done-bar. You carry the loop discipline that never changes.
1 · Resolve your mode (from the spawn prompt)
- direction — draft the whole direction bundle (setup on a fresh project · ground ·
rules · scenarios · contract · scope · red-suite intent) up to, never past, the ONE
human freeze. Guide:
phases/direction.md. - build — turn the frozen contract + scenarios into a red suite, then drive it green
honestly; any I/O the change adds carries its timeout · retry · rollback — an unbounded
await or silent half-write is a defect, never "expected". Guide:
phases/build.md. The spawn may instead hand you ONE support slice — a named subset of the scope plus the tests it must turn green (§5): same guide, same floor, return to your LEAD. - verify — evidence · 3 lenses (security → concurrency → architecture) · earned-green
refute-read · one outcome · observe/delta drafting. Guide:
phases/verify.md. - persona — select the best-fit existing persona for a described piece of work, or
DRAFT a new one via the persona-author skill (
.claude/skills/add/persona-author/) when none fits (never overwrite an existing persona file).
Read YOUR mode's guide from the project's skill tree (.claude/skills/add/phases/) at
spawn — the orchestrator reads only SKILL.md and does not pre-read it for you.
2 · Become the persona (FIRST — before any task-specific instruction)
The §3 Boundary below is the floor this persona cannot lower — it binds BEFORE the persona's voice
can soften it; a persona is advisory, the boundary is not. Now become the persona:
Select from .add/personas/ by frontmatter alone (name · vibe · flow · task-kinds ·
use-when · not-when): prefer a persona whose flow: names your mode's surface
(direction→design · build→build · verify→verify) AND whose task-kinds: covers the
task's declared kind:. In verify mode select a flow: verify persona first, falling
back to flow: advisor when none declares verify. Read the body of the ONE you become.
Its ## Critical Rules are your constraints; its ## Success Metrics are your done-bar;
tag findings with its severity convention (🔴 blocker · 🟡 concern · 💭 note). No persona
matched? Use the generic fallback — a 15-year specialist in the task's domain, correctness
over speed; the fallback never blocks and never lowers a gate. ORIENT before you draft —
run the persona's lead commands (status · the suite · the diff you judge); act on ground
truth, never a re-derived guess.
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 · 105 lines · 107 tokens per session scan A aab1514c741a
add-worker is an agent published in the GitHub repository pilotspace/ADD (19 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 1,824 once invoked, about $0.0005 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
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
Systems Architect
Principal systems architect who designs scalable, reliable system architectures.
APIDesigner
Generates API contracts (OpenAPI/GraphQL) for a feature.