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 skills add Innocent-children/dev-flow --skill dev-flowgit clone --depth 1 https://github.com/Innocent-children/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/skills/innocent-children/dev-flow/dev-flow)<a href="https://agentmods.dev/skills/innocent-children/dev-flow/dev-flow"><img src="https://agentmods.dev/badge/skills/innocent-children/dev-flow/dev-flow/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/skills/innocent-children/dev-flow/dev-flow"><img src="https://agentmods.dev/badge/skills/innocent-children/dev-flow/dev-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00561 |
| Opus 5.5 | $0.00009 | $0.00224 |
| Sonnet 5.5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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 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.
What it actually says
Dev Flow for Claude Code
Use /dev-flow-claude:dev-flow for assessment. Claude performs repository work and authorized Host
operations; Core owns Task state, Actions, transitions, verification, blockers and recovery.
Invocation does not authorize Git changes or approve an unseen plan. Reuse valid user answers.
| Request or state | Read and perform |
|---|---|
| New development request | Admission: assess read-only, obtain missing choices, then prepare every confirmed repository; default to a new local branch. |
| Saved launch | Read its status/receipt and actual workspace identity through admission before creation/resume; a requested Claude session does not prove Core creation. |
| Existing Task | Return to the original workspace and connect/resume, without preparing another workspace or creating another Task. |
| Current Action | Action execution and only the current node guide. |
| Rejection, lost result or blocker | Response handling and its linked recovery procedure. |
| Installation, relocation, cancellation, abandonment or cleanup | Host lifecycle. |
After provisioning or on resume, perform server_info
first and require Claude support. Use actually visible tools through transport.
Retain full responses, inspect ok, then recovery/blocker/outcome and the complete Action.
Follow the Action procedure for requirements/design discussion, saved-plan approval, method steps and submission. Use artifacts before writes and every submission, and verification for checks. Required user decisions stay with the user. Write/Edit/NotebookEdit require the trusted PreToolUse Hook; a denial or disabled gate cannot be bypassed with another tool. Bash/external writes are observed later. Claude permissions still apply.
Follow current user and CLAUDE.md/AGENTS.md instructions. Confirm every repository (at most eight) and its permissions before preparation; never create a partial Task. Indexes are optional and are not installed automatically. Read handoff before another session. DONE/CANCELLED preserves local work and grants no commit, push, publication or deletion authority; dedicated worktree and branch deletion require their separate authorization.
Implementation: packages/claude/lib/workspace.mjs; packages/claude/bin/dev-flow-claude.mjs;
packages/claude/plugin/hooks/pre-tool-use.mjs.
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/admission.md 12 KB
- references/artifact-contract.md 7.5 KB
- references/artifacts.md 2.5 KB
- references/connection-examples.md 11 KB
- references/connection.md 5.8 KB
- references/core-lifecycle-examples.md 6.2 KB
- references/core-lifecycle.md 4.0 KB
- references/host-lifecycle.md 6.3 KB
- references/method-profiles.md 18 KB
- references/node-payloads.md 5.8 KB
- references/nodes/comprehension-examples.md 18 KB
- references/nodes/comprehension.md 4.5 KB
- references/nodes/delivery-examples.md 17 KB
- references/nodes/delivery.md 4.7 KB
- references/nodes/design-examples.md 6.0 KB
- references/nodes/design.md 2.5 KB
- references/nodes/implementation-examples.md 11 KB
- references/nodes/implementation.md 3.4 KB
- references/nodes/refactor-examples.md 8.3 KB
- references/nodes/refactor.md 2.8 KB
- references/nodes/requirements-examples.md 3.3 KB
- references/nodes/requirements.md 2.3 KB
- references/nodes/tasks-examples.md 13 KB
- references/nodes/tasks.md 5.0 KB
- references/nodes/test-examples.md 20 KB
- references/nodes/test.md 6.0 KB
- references/recovery-examples.md 9.6 KB
- references/recovery.md 4.8 KB
- references/response-examples.md 3.4 KB
- references/successes/dev_flow_abandon_task-abandon.md 4.9 KB
- references/successes/dev_flow_cancel_task-cancel.md 4.8 KB
- references/successes/dev_flow_get_next_action-guarded-read.md 4.5 KB
- references/successes/dev_flow_get_task-read.md 7.6 KB
- references/successes/dev_flow_open_task-create.md 8.3 KB
- references/successes/dev_flow_open_task-multiple.md 10 KB
- references/successes/dev_flow_open_task-resume.md 7.6 KB
- references/successes/dev_flow_prepare_task_relocation-prepare.md 8.0 KB
- references/successes/dev_flow_recover_action-saved-operation.md 8.1 KB
- references/successes/dev_flow_resolve_blocker-allow_once.md 13 KB
- references/successes/dev_flow_resolve_blocker-expand_scope.md 11 KB
- references/successes/dev_flow_resolve_blocker-history.md 12 KB
- references/successes/dev_flow_resolve_blocker-reject.md 13 KB
- references/successes/dev_flow_resolve_blocker-relocation.md 12 KB
- references/successes/dev_flow_resolve_blocker-verification-or-recovery.md 17 KB
- references/successes/dev_flow_server_info-handshake.md 2.4 KB
- references/successes/dev_flow_submit_comprehension-code_too_complex.md 14 KB
- references/successes/dev_flow_submit_comprehension-comprehension_passed.md 17 KB
- references/successes/dev_flow_submit_comprehension-design_too_complex.md 11 KB
- references/successes/dev_flow_submit_comprehension-evidence_insufficient.md 16 KB
- references/successes/dev_flow_submit_comprehension-implementation_defect.md 15 KB
- references/successes/dev_flow_submit_comprehension-requirement_unclear.md 11 KB
- references/successes/dev_flow_submit_delivery-delivery_complete.md 12 KB
- references/successes/dev_flow_submit_delivery-delivery_needs_comprehension.md 16 KB
- references/successes/dev_flow_submit_delivery-delivery_needs_design.md 12 KB
- references/successes/dev_flow_submit_delivery-delivery_needs_implementation.md 15 KB
- references/successes/dev_flow_submit_delivery-delivery_needs_requirements.md 11 KB
- references/successes/dev_flow_submit_delivery-delivery_needs_test.md 16 KB
- references/successes/dev_flow_submit_design-design_ready.md 11 KB
- references/successes/dev_flow_submit_design-design_requires_requirements.md 8.8 KB
- references/successes/dev_flow_submit_implementation-implementation_needs_refactor.md 13 KB
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 Changed · +10 lines 3fefe44d1d14
- 1mo ago Changed · -108 lines · -53 tokens per session 96a6438cd451
- 1mo ago Changed · -709 lines · +10 tokens per session 5d0a89426593
- 1mo ago Changed · +163 lines 4ac18fbb23f4
- 1mo ago Changed · +8 lines 45b4a0df8d30
- 1mo ago Changed · +198 lines · -18 tokens per session 80f7130c5371
- 1mo ago First seen · 477 lines · 84 tokens per session scan A d7368fd07e5e
dev-flow is a skill published in the GitHub repository Innocent-children/dev-flow (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 561 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 skills, from other repositories
git-workflow-and-versioning
Plan, implement, or review git workflow and versioning work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests git workflow and versioning work.
git-commit
Plan, implement, or review git commit work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests git commit work.
make-repo-contribution
Plan, implement, or review make repo contribution work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests make repo contribution work.
finishing-a-development-branch
Plan, implement, or review finishing a development branch work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests finishing a development branch work.
final-release-review
Plan, implement, or review final release review work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests final release review work.
pr-draft-summary
Plan, implement, or review pr draft summary work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests pr draft summary work.