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 skills/cofin/flow/flow-planningnpx skills add cofin/flow --skill flow-planninggit clone --depth 1 https://github.com/cofin/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.00038 | $0.00926 |
| Opus 5 | $0.00019 | $0.00463 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
flow-planning 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Planning
Trigger
Use for prd|plan|refine|revise|research|task.
interaction_authority: skills/flow/references/interaction.md
planning_loop:
phases: [research_closed, draft, gap_scan, refine, revision_update, review, approved, revise, blocked]
gap_scan:
reject: [deferred_research, unresolved_decisions, stub_body, vague_verification, missing_verification_strategy, overlapping_ownership, oversized_task]
require: [requirement_to_task_traceability, one_invocation_per_task, one_commit_per_task]
revision_update:
on_plan_change: [increment_plan_revision_once, copy_revision_to_spec_and_all_tasks, clear_plan_commit, rerun_validation]
review:
max_external_rounds: 3
blocking_severities: [Critical, Important]
on_limit: blocked
Workflow
- Research & Frontier Analysis: Close codebase facts autonomously using background
@researchersubagents. Map design choices as an unblocked frontier with opinionated recommendations (❓ Choice [ID] ... ➡️ Recommendation). - Multi-Interface Exploration: Explore competing interface designs and evaluate structural boundaries using
architecture-criticbefore spec lock. - Draft Spec & Worksheets: Write
spec.mdand complete worksheets intasks/<short_id>.mdspecifying public interfaces, types, and testing seams. - Adversarial Stress-Testing: Apply the
devils-advocatelens before presenting for approval to catch edge cases. - Approval Gate: Present
Approve|Revise|Refine. Upon approval, hand off toflow-execution.
Guardrails
- Planning modifies files exclusively under
.agents/bundles/specs/<flow_id>/. Never edit application source code during planning. - A plan is Ready only when a zero-context agent can implement every task correctly from the worksheet alone.
- Every task must be sized for exactly one subagent invocation and one atomic Git commit.
- Select exactly one verification strategy from the maintained matrix below.
What ships with it
1 file 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.
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.
- 2d ago First seen · 75 lines · 38 tokens per session scan A d5be6d4e0ba3
flow-planning is a skill published in the GitHub repository cofin/flow (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 926 once invoked, about $0.0002 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-30.
Other skills, from other repositories
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.