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 cofin/flow --skill flow-executiongit clone --depth 1 https://github.com/cofin/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/cofin/flow/flow-execution)<a href="https://agentmods.dev/skills/cofin/flow/flow-execution"><img src="https://agentmods.dev/badge/skills/cofin/flow/flow-execution/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/cofin/flow/flow-execution"><img src="https://agentmods.dev/badge/skills/cofin/flow/flow-execution.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.00050 | $0.00739 |
| Opus 5.5 | $0.00020 | $0.00296 |
| Sonnet 5.5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
flow-execution 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Execution
Trigger
Use for implement only, after a validated plan contains ready task worksheets.
contract: worksheet-execution-v1
invariants:
- worksheet-first
- fail-closed-no-production-mutation
- fresh-validated-plan-resume
transitions:
- preflight-claim
- mismatch-discover-block
- nonblocking-discover-release
- revised-plan-resume
authority: skills/flow/references/implement.md
Workflow
- Preflight: Inspect
.agents/bundles/specs/<flow_id>/tasks/<short_id>.md, verify dependencies areclosed, and apply a journaledclaimthroughflow-statewith the expected plan identity and spec state revision. - Initial Evidence: Collect the declared strategy's required initial proof; only behavior and regression strategies require red.
- Minimal Implementation: Make the smallest task-owned change while keeping focused evidence green.
- Quality Gates: Run repository linters and typecheckers while tests remain green.
- Atomic Commit & Close: Stage exact files, commit, apply a journaled
closethroughflow-staterecordingcommit: <sha>, and reconcile thespec.mdchecklist via/flow:sync.
Guardrails
- Execute exactly one task per subagent dispatch.
- Never mark a task
closedwithout running the test command and observing exit code 0. - Stage only task-owned files; never perform opportunistic unrelated edits.
- Work on the active branch. Never create or mutate Git tags.
Strategy Evidence
| Strategy | Initial evidence | Final evidence |
|---|---|---|
behavior_tdd |
Focused behavior test fails because behavior is absent. | Focused test and relevant aggregate verification pass. |
regression_tdd |
Focused reproduction fails with the reported symptom. | Regression and relevant aggregate verification pass. |
characterization |
Focused behavior baseline passes before cleanup. | Same behavior passes unchanged; compare affected coverage when needed. |
static_validation |
Native parser, lint, type, build, or generator baseline runs. | Isolated representative violation produces the expected diagnostic; restored focused and aggregate gates pass. |
documentation_validation |
Documentation-native baseline runs. | Documentation checks and promised examples pass. |
integration_acceptance |
Focused integration baseline passes. | End-to-end scenario passes; injected negative states prove refusal paths. |
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.
- 1mo ago First seen · 72 lines · 50 tokens per session scan A 1eb1065e2756
flow-execution is a skill published in the GitHub repository cofin/flow (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 739 once invoked, about $0.0002 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-30.
Other skills, from other repositories
bds-workflow
10-step beads-starter workflow guide. Runs only on explicit invocation.
work-beads
Use for /work-beads, a requested Beads backlog batch, or implementation of named bead IDs.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…