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/arsxxi/iterative-dev-workflow/phase-3git clone --depth 1 https://github.com/Arsxxi/iterative-dev-workflowWhat 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.00006 | $0.00587 |
| Opus 5 | $0.00003 | $0.00293 |
| Sonnet 5 | $0.00001 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
phase-3 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
Kilo Code does not substitute $ARGUMENTS. Wherever this command refers to
$ARGUMENTS, read it as the text I typed after the slash command in this message.
Expected: project name
If I typed nothing after the command, do not guess and do not invent a value: ask me
for it with the question tool, then continue from there.
Step 0 — find which project this is for
Before anything else, figure out which project this command applies to:
- If you were given a project name after the slash (e.g.
/phase-3 my-project), use it. - Otherwise, look at the subfolders under
.workflow/:- Exactly one folder → use it. Tell the user which project you picked (e.g. "Working on
my-project"), so it's never a silent guess. - Two or more folders → ask the user once which project this is for. To make the question
useful, show the first line of each project's
00-context.md, not just the folder name. - No folders → stop and tell the user to run
/kickofffirst. Don't proceed.
- Exactly one folder → use it. Tell the user which project you picked (e.g. "Working on
Phase 3: Implementation Plan
Purpose
Write a comprehensive implementation plan based on the proposed plan and extensive architecture and design from Phase 1 and Phase 2.
Steps
- Check for the previous result from the previous step. If it's empty or not generated due to certain reason, then DO NOT PROCEED TO EXECUTE THIS STEP. Don't forget to remind the user if this happened.
- Write a comprehensive implementation plan based on the proposed plan (Phase 1: Analyze) and extensive architecture and design (Phase 2: Design - the chosen design, ATAM trade-offs, Quality Attribute results, System Context Diagram, and User Journey Diagram).
Constraints
AVOID overengineering, PREFER simple, low-complexity implementations with the GOAL of high maintainability, AVOID jargons when naming function/methods/class/components/system, instead PRIORITIZE using layman's terms or prefer naming with the actual intentions of the code, the GOAL is ease of developer understanding and maintainability.
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 · 57 lines · 6 tokens per session scan A 633b5d89ac34
phase-3 is a command published in the GitHub repository Arsxxi/iterative-dev-workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 587 once invoked, about $0.0000 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-31.
Other commands, from other repositories
spec
Start spec-driven development — write a structured specification before writing code.
toh-help
Display all Toh Framework commands and quick usage guide.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
notebook-status
Check the progress of a /agy:notebook sweep (for long document sets run with --background). Reports % complete, done/pending/failed counts, elapsed time and a rough ETA, and which documents are still pending — so you can resume. Read-only, no agy.
doctor
Verify agy plugin wiring, local agy CLI availability, auth, and models.
models
List models available to the local Antigravity (agy) CLI.