A single entry point for a software development planning workflow. It covers research, planning, design decisions, task breakdown, implementation, progress tracking, review, and release.

Researching a problem, writing a business and implementation plan, discussing design choices, creating phase tasks, and guiding development through review and release.

It gives a coding project one guided path from an idea to shipped work. This helps keep decisions, plans, and tasks connected.

the-flow — Skill for Claude Code and Codex by jakkaj/tools

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.

Any agent

npx skills add jakkaj/tools --skill the-flow

Clone the repo

git clone --depth 1 https://github.com/jakkaj/tools

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jakkaj/tools/the-flow/github.svg)](https://agentmods.dev/skills/jakkaj/tools/the-flow)

Your own site

<a href="https://agentmods.dev/skills/jakkaj/tools/the-flow"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/the-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jakkaj/tools/the-flow"><img src="https://agentmods.dev/badge/skills/jakkaj/tools/the-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 252 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,898 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00252	$0.04898
Opus 5.5	$0.00101	$0.01959
Sonnet 5.5	$0.00050	$0.00980
Haiku 4.5	$0.00025	$0.00490

Measured 2mo ago against content hash 34a961e4e122, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

the-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 2mo 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.

skills/SDD/the-flow/SKILL.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/the-flow — SDD pipeline dispatch

One public skill for the whole SDD pipeline, built to the flow-architecture pattern (docs/skills-pipeline/flow-architecture.md): the sub-skills (contract-bound verbs, one per stage) live in references/stages/, the guided-mode engine in references/00-routing.md, the coaching voice in references/coach.md. New to the flow? references/getting-started.md.

Progressive disclosure is the contract: load exactly one sub-skill for the current step — never read all of them up front.

Two load paths

Guided — /the-flow (no args, or <slug> / <ord>-<slug>):

Read references/00-routing.md (entry paths, state contract, the Graph) and references/coach.md (rail, narration, print-then-offer).
Resolve fresh / resume / adopt per 00-routing.md; load only the current stage's sub-skill when a step is accepted, and coach the seam.
Guided mode owns all the-flow state, and drives all of it — position and session bag — through harness flow nav calls: the flight plan (the-flow.json → the-flow.md) is the single state substrate (plan 024 — the CLI is the generator; nothing is hand-written; run the capability precheck first, § Prerequisite). Before the first flight-plan mutation of a session, also load references/flight-plan-ops.md — the nav model, the spine-vs-excursion rule, and the verb flags + gotchas (loaded on demand, not up front; sub-skills never load it).

Direct jump — /the-flow <id> <verb> [flags]:

Resolve the stage via the Registry below. Id and verb each resolve alone (typing 6 ≡ typing implement); when both are given they must name the same stage — if they disagree, show the Registry and ask which was meant (never guess).
Read only that sub-skill and follow it with the given flags (same flags the verb has always taken).
No coach, no rail, no state writes — and no harness seams (harness orchestration is the guided engine's job — direct-jump runs the bare verb, harness-less by design). Artifacts land where they always did; the next guided run discovers them by existence and catches state up.

Read the full file on GitHub · 115 lines

Files

What ships with it

19 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.

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.

2mo ago First seen · 115 lines · 252 tokens per session scan A 34a961e4e122

Subscribe to this mod's changes

the-flow is a skill published in the GitHub repository jakkaj/tools (5 stars, last pushed 24d ago), licensed MIT. It adds 252 tokens to every session and 4,898 once invoked, about $0.0010 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.

Planning

the-flow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
the-flowjakkaj/tools	Skill	5	24d ago	MIT	A	252	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code