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.
git clone --depth 1 https://github.com/daphnee-ovo/dev-flowWrote 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/daphnee-ovo/dev-flow/init)<a href="https://agentmods.dev/commands/daphnee-ovo/dev-flow/init"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/daphnee-ovo/dev-flow/init"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/init.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01716 |
| Opus 5.5 | $0.00008 | $0.00686 |
| Sonnet 5.5 | $0.00004 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
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 1mo 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INIT — Project Initialization
General Principles
/init is the entry command for dev-flow. After execution, guarantee:
.dev-doc/directory structure complies with spec- All document formats pass validation
- Persistent docs (
docs/) initialized and populated - Project-level agent instruction file correctly reflects project info
- Project state consistent with reality
Execution Flow
Phase 1: Environment Detection + Project Scan
Run scan to get project info:
dow scan
Outputs project name, tech stack, commands, directory structure, git status, existing .dev-doc etc.
Judge path based on output:
- Output shows
dev_doc: none→ Path A (brand new project) - Otherwise → Path B (existing project)
Phase 2A: Brand New Project Initialization
- Ask for project name and dev mode (skip asking if scan output has clear info)
- Execute initialization:
Auto-creates directory structure (.dev-doc/{issue,task,archive}, tests, tmp), writes STATUS.yaml and project root VERSION (multi-branch format). Also generates persistent doc skeleton (README.md + docs/{structure,decisions,usage}.md) and registers in STATUS.yaml. If project already hasdow init --name <project_name> --mode <mode>tempdirectory, reuse it, don't createtmp. Existing doc files won't be overwritten. - Jump to Phase 4
Phase 2B: Existing Project Alignment
2B-1. State Inference
Judge actual phase based on script scan results:
| Condition | Inferred Phase |
|---|---|
| Has code + has passing tests + has TEST.md | DONE or TEST |
| Has code + has TASK.md partially complete | DEV |
| Has SPEC.md but no/little code | TASK or SPEC |
| Has PRD.md but no SPEC.md | PRD → SPEC |
| Only README or scattered code | Determine initial phase by mode |
Initial phase by mode:
| Mode | Initial Phase | Description |
|---|---|---|
full |
PRD | Start from requirements definition |
quick |
SPEC | Skip requirement exploration |
fast |
TASK | Directly decompose tasks |
mvp |
SPEC | Quick validation path (brainstorm → spec → dev) |
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.
- 1mo ago First seen · 232 lines · 20 tokens per session scan A b1c23f59cfca
init is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,716 once invoked, about $0.0001 per session on Opus 5.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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
set-tracker
Set the issue tracker for the current project.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
orchestrate
You are the Project Orchestrator, the ultimate enforcer of the NASAB framework principles in all project workflows. You coordinate multi-agent work while ruthlessly enforcing quality gates, capability validation, and the principle of Patience (Pillar 6): perfect before advancing.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.