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/issue)<a href="https://agentmods.dev/commands/daphnee-ovo/dev-flow/issue"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/issue/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/issue"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/issue.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.00004 | $0.00731 |
| Opus 5.5 | $0.00002 | $0.00292 |
| Sonnet 5.5 | $0.00001 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
issue 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ISSUE — Manual Issue Creation
Mode Detection
DOC_ROOT obtained via dow status --field doc_root.
Execution Steps
1. Collect Information
Ask user (can get from parameters):
- Issue title
- Severity (P0/P1/P2)
- Location found (file_path:line_number)
- Description
2. Determine File
Check if today's other source issue file already exists:
dow issue list | grep 'other'
- If exists and file has reasonable issue count (<10) → append to existing file
- Otherwise → create new file
3. Create Issue
dow issue create --title "..." --severity P1 --location "file:line" --desc "..." --source other \
--file '{"modify":["src/bug.rs"]}'
Also supports stdin JSON. The input can be one object or an array; an array is created as one batch and receives IDs in input order:
echo '{"title":"bug","severity":"P0","location":"main.rs:10","desc":"crash on startup","reproduce":"run command","source":"other","files":{"modify":["main.rs"]}}' | dow issue create
echo '[{"title":"bug 1","severity":"P1","location":"a.rs:1","desc":"...","reproduce":"...","source":"other","files":{"modify":["a.rs"]}},{"title":"bug 2","severity":"P1","location":"b.rs:2","desc":"...","reproduce":"...","source":"other","files":{"create":["b.rs"]}}]' | dow issue create
The required fields are title, severity, location, desc, reproduce,
source, and files. Within files, create and modify are individually
optional, but at least one must contain a non-empty path:
dow issue create --file '{"modify":["src/a.rs","src/b.rs"],"create":["tests/a.rs"]}'
Use dow issue schema for the authoritative field definition. files_test,
flat files_modify/files_create, and --files-* flags are not accepted.
4. Write Format
Execute dow issue schema to get structured format definition.
5. Prompt Next Step
[dev-flow] Issue created: .dev-doc/issue/<filename>
To repair open issues, explicitly invoke /fix when ready.
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 · 92 lines · 4 tokens per session scan A 2adf7f2ddf62
issue is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 731 once invoked, about $0.0000 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.