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-completionnpx skills add cofin/flow --skill flow-completiongit 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.00030 | $0.00456 |
| Opus 5 | $0.00015 | $0.00228 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
flow-completion 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.
What it actually says
Flow Completion
Trigger
Use for review|finish|archive|revert|docs|cleanup|validate.
contract: quality-completion-v1
authority: skills/flow/references/review.md
finish_gates: [verification, code_review, quality_review, finish]
archive_gates: [archive_candidate, verification, code_review, quality_review, archive]
runtime_dependency: agent_file_tools_only
evaluator_module: forbidden
Workflow
- Two-Axis Review (
/flow:review): Run parallel reviewers evaluating Standards/Smells (Security, Performance, Debloat lenses) and Spec Conformance againstgit diff <base>...HEAD. - Finish Flow (
/flow:finish): Run full test verification suite and record single-paragraph ADRs inknowledge/decisions/. - Archive Flow (
/flow:archive): Synthesize discoveries into project-shaped knowledge, append onelog.mdentry, and delete the reviewed completed spec inventory through a journaled archive operation. - Revert or Validate: Revert designated changes or run repository validation checks.
Guardrails
- Reviews are read-only; report concrete evidence with file/symbol references.
- Archive leaves a terminal journal outside the bundle and no resident archived spec.
- Preserve Git history. Never create or mutate Git tags.
Output
Return the review assessment, verification evidence, ADR summaries, or archived flow manifest.
Validation
Confirm test suites pass cleanly, no blocking review findings remain, and knowledge synthesis is complete.
Example
For flow completion, run tests, review the diff against main, elevate reusable patterns to evidence-backed knowledge/patterns/<topic>.md chapters, and archive the spec directory.
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 · 50 lines · 30 tokens per session scan A 1b6ea93aa8d7
flow-completion is a skill published in the GitHub repository cofin/flow (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 30 tokens to every session and 456 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.