dev-flow

A command that guides a software change through investigation, planning, implementation, testing, and code review. It includes an architecture review and asks for approval before implementation.

In plain words
What is it for?
Use it to take a feature or fix from an initial code investigation to an approved plan, working implementation, quality checks, and resolved review comments.
Why use it?
It gives feature work or bug fixes a defined sequence, so important design, testing, and review steps are not skipped.

Command

Install

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.

agentmods
npx agentmods add commands/addit-digital/addit-harness/dev-flow
Clone the repo
git clone --depth 1 https://github.com/addit-digital/addit-harness
Per session 117 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00117 $0.00274
Opus 5 $0.00059 $0.00137
Sonnet 5 $0.00023 $0.00055
Haiku 4.5 $0.00012 $0.00027

Measured 2d ago against content hash 7c74aeab6853, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-flow 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.

commands/dev-flow.md · 17 lines

What it actually says

Invoke the addit-harness:dev-flow skill via the Skill tool now, forwarding any arguments given after the command: "$ARGUMENTS".

Changes

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.

  1. 2d ago First seen · 17 lines · 117 tokens per session scan A 7c74aeab6853

Subscribe to this mod's changes

dev-flow is a command published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 10d ago), licensed MIT. It adds 117 tokens to every session and 274 once invoked, about $0.0006 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.