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/daphnee-ovo/dev-flow/iterategit clone --depth 1 https://github.com/daphnee-ovo/dev-flowWhat 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.00014 | $0.02036 |
| Opus 5 | $0.00007 | $0.01018 |
| Sonnet 5 | $0.00003 | $0.00407 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
iterate 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ITERATE — Iteration Delivery
General Principles
/iterate is dev-flow's iteration wrap-up command. After execution completes current version delivery and starts next iteration.
Includes all responsibilities of original /done (delivery check) and original /iterate (archive + reset).
Pre-checks (blocking)
dow iterate auto-executes, stops if any fails:
- All tasks in task files must be checked
[x](audit mode skips) - No unclosed P0 issues
- VERSION file exists and format legal
- All CI steps in
.dev-doc/preIterate.cimust succeed (if file exists)
Parameters
| Parameter | Description | Default |
|---|---|---|
--topic |
Archive topic (for archive directory naming) | Required |
--type |
commit type (feat/fix/refactor/docs/perf/test/style/workflow) | Required |
--files |
Additional source code files/directories to commit (space-separated). No need to pass .dev-doc/ files — they're auto-managed by iterate (archive delete + git add -u). Paths are validated before preIterate executes — do not include files that will be dynamically generated by preIterate steps (those are auto-collected). |
Optional |
-v/--bump |
Version increment type: major/minor/patch | patch |
--tag |
Force create git tag for patch bump | - |
--confirm |
Confirmation token (ITR-xxxxxx, from preview output) |
- |
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 · 170 lines · 14 tokens per session scan A 81d63111b0e8
iterate is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed 17d ago), licensed MIT. It adds 14 tokens to every session and 2,036 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-31.
Other commands, from other repositories
sc-detail
Throughline の退避済みターン（L2 本文 + L3 ツール入出力）を時刻で復元する.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
motion
Runtime entry point for configuring global motion tokens, scroll-reveals, and micro-delight interactions in motion.js and interactions.js.
perf
Runtime entry point for checking asset performance budgets, script preconnects, and load optimization. Part of the Quality & Audit lifecycle phase.
assets
Runtime entry point for generating AI media, removing image backgrounds, and optimizing image payloads.
tokens
Establish the single source of truth every other command reads from. This is the one command every later command depends on — re-running it (a rebrand, a palette fix) is how a change propagates to every page at once.