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 instructions/daphnee-ovo/dev-flow/agents-mdgit 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.01675 | $0.01675 |
| Opus 5 | $0.00838 | $0.00838 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
dev-flow AGENTS.md 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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev-Flow Plugin
项目全流程管理插件，从需求探索到交付的完整生命周期管理。
Language Policy
- Use English consistently for default workflow prompts, skill metadata, generated artifacts, build output, and new user-facing messages.
- Keep non-English text only in explicitly localized files, such as
README.zh-CN.md, or when preserving user-provided content.
注意事项
- 禁止直接在开发环境测试导致开发环境的流程管理被污染。如需测试，需要在./tmp/test_target_project 中进行测试
- 严禁更新 A agent 相关内容的时候导致 B agent的支持被破坏
命令
| 命令 | 作用 |
|---|---|
/init |
初始化 dev-flow 项目（创建 .dev-doc、选择模式） |
/brainstorm |
实现前的协作式需求探索与设计 |
/prd |
启动 PRD agent，进入需求探索阶段 |
/spec |
启动 SPEC agent，进入技术规范阶段 |
/task |
启动 TASK agent，进入任务拆解阶段 |
/issue |
手动创建 issue 文件 |
/fix |
User-triggered workflow: read, claim, fix, verify, and close open issues |
/test |
执行 dow test 全量测试 |
/status |
报告当前项目状态和进度 |
/check |
执行 dow doctor 检查文档和项目状态 |
/iterate |
迭代交付（检查 + 归档 + commit & tag + bump） |
/mode |
选择开发模式（full/quick/fast/mvp；audit 为自动触发） |
流程
头脑风暴(BRAINSTORM) → 需求(PRD) → 规范(SPEC) → 任务(TASK) → 开发(DEV) → 测试(TEST) → 迭代(ITERATE) → 下一轮
可选 │ ↑
│ 例行TEST │
│ (任务级循环) │ 项目TEST
└───────────────→│
dow CLI
PATH 中的 dow（默认安装路径为 ~/.local/bin/dow） 是 Rust 编写的统一调度器，所有 hook 和脚本化操作通过它执行。
| 子命令 | 作用 |
|---|---|
dow status |
读取 STATUS.yaml |
dow status set --phase/--mode/--exec-mode/--name/--goals-minor/--goals-major |
更新 STATUS.yaml 字段 |
dow doctor [--fix] |
统一诊断、校验并可修复 .dev-doc；dow fix 是兼容别名 |
dow issue list [--all] |
列出 issue |
dow iterate --topic <t> --type <type> [--files f1 f2...] [-v minor] [--confirm ITR-xxxxxx] |
迭代交付 |
dow scan |
项目扫描 |
dow task/issue/prd/spec/brainstorm/changelog schema |
获取对应资源的格式定义 |
dow test |
全量测试 |
dow test <TASK-ID> |
执行指定 Task 关联的测试 |
dow archive list [--branch <b>] |
列出所有归档版本 |
dow archive show <version> |
某版本归档详情 |
dow archive tasks [--version v] [--priority P0] |
查询归档任务 |
dow archive issues [--version v] [--severity P0] |
查询归档 issue |
dow archive doc <version> <PRD|SPEC|TEST|BRAINSTORM> |
输出归档文档原文 |
dow archive migrate [--delete-originals] |
从目录迁移到 SQLite |
dow archive stats |
归档统计 |
dow hooks context [--codex-hook] |
hook：注入上下文；Codex hook 使用协议 JSON envelope |
dow hooks guard <file> |
hook：文件写入守护 |
dow hooks post-write <file> |
hook：写后联动 |
dow hooks save-changelog [--codex-hook] |
hook：保存 CHANGELOG；Codex hook 使用 Stop 协议 JSON |
dow version [--set X.Y.Z] [--bump major|minor|patch] |
读写 VERSION |
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.
- yesterday First seen · 123 lines · 1,675 tokens per session scan A 8ad2a77aa03e
dev-flow AGENTS.md is an instructions file published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed 16d ago), licensed MIT. It adds 1,675 tokens to every session, about $0.0084 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 instructions, from other repositories
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
cloudx AGENTS.md
AGENTS.md instructions for davidomil/cloudx, covering cloudx repository instructions, purpose, sources of truth, required change process and engineering rules.
codex-bee AGENTS.md
AGENTS.md instructions for usulpro/codex-bee, covering agents.md, project summary, product goals, current stack and working agreements.
cezar AGENTS.md
Instructions for open-mercato/cezar, covering agents.md — working in this repository, zero config, changing a mechanism that already works, the http api and repository layout.
ai-driven-development AGENTS.md
Instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
roamcode AGENTS.md
Instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.