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/fixgit 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.00009 | $0.00499 |
| Opus 5 | $0.00005 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
fix 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.
What it actually says
FIX — User-triggered automatic issue repair
Only run this workflow when the user explicitly invokes /fix. Do not invoke
it automatically from hooks, /test, /check, task completion, or issue
creation.
Execution
-
List open issues with
dow issue list. The CLI resolves the active branch's document root. If there are no open issues, report that and stop. -
Read each issue with
dow issue show <ISSUE-ID>and understand its scope, reproduction steps, affected files, and any related task or specification. -
Claim every issue before making project changes:
dow claim <ISSUE-ID>... -
Fix each claimed issue. Locate the root cause, keep the change scoped to the issue, and run appropriate verification. Bug fixes require a regression test; if that is technically infeasible, explain the alternative verification and ask the user before closing the issue.
-
For a verified fix, record the result and close the issue:
dow issue update <ISSUE-ID> --fix "<concise fix summary>" dow issue close <ISSUE-ID>dow issue closechecks the issue, renames a fully closed issue file, and revokes its claim. Do not edit the issue checkbox or rename issue files manually. If update or close fails, do not report the issue as fixed. -
Leave unfixable issues open. Report the reason, verification performed, and the suggested next step.
Completion Report
Summarize every issue handled:
[dev-flow] Issue Fix Report
Fixed: N
Cannot fix: M
Blocked: K
Details:
✓ <issue-id>: <one-sentence fix and verification summary>
✗ <issue-id>: <reason and next step>
! <issue-id>: <claim or workflow blocker>
Audit Mode
When the mode is audit/<original_mode> (for example, audit/quick), the fix
workflow is unchanged. After all issues are fixed, prompt the user to run
/iterate; /iterate restores the original mode after completion.
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 · 67 lines · 9 tokens per session scan A 59887d0e512b
fix is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed 17d ago), licensed MIT. It adds 9 tokens to every session and 499 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
ox-session-review
Command "ox-session-review" from sageox/agentx, covering phase 1 — scan & score (read-only), quality signals, removal candidates, missing/poor summary and poor title.
sc-detail
Throughline の退避済みターン（L2 本文 + L3 ツール入出力）を時刻で復元する.
motion
Runtime entry point for configuring global motion tokens, scroll-reveals, and micro-delight interactions in motion.js and interactions.js.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
perf
Runtime entry point for checking asset performance budgets, script preconnects, and load optimization. Part of the Quality & Audit lifecycle phase.
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.