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 HigorAlves/orc --skill flow-phasesgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/flow-phases)<a href="https://agentmods.dev/skills/higoralves/orc/flow-phases"><img src="https://agentmods.dev/badge/skills/higoralves/orc/flow-phases.svg" alt="Measured on agentmods" height="20"></a>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.00062 | $0.00435 |
| Opus 5 | $0.00031 | $0.00217 |
| Sonnet 5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
flow-phases 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 4d 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 Phases
The phase bodies of /orc:flow, disclosed progressively — the command's entry point carries routing, triage, and the gates; each phase's full playbook loads only when the flow reaches it.
Protocol: entering phase N → Read exactly references/PHASE-<N>-<NAME>.md, then execute it. Never run a phase from memory, never read phases ahead of the one being entered, and never read a phase the run skips.
| Phase | File |
|---|---|
| 2 — RFC (optional) | PHASE-2-RFC.md |
| 3 — Plan | PHASE-3-PLAN.md |
| 4 — Start (worktree + failing test) | PHASE-4-START.md |
| 5 — Implement (orc-implementer batches) | PHASE-5-IMPLEMENT.md |
| 6 — QA | PHASE-6-QA.md |
| 7 — Ship | PHASE-7-SHIP.md |
| 8 — Address | PHASE-8-ADDRESS.md |
| 9 — Cleanup | PHASE-9-CLEANUP.md |
Phases 0–1 (context detection, triage, the sprint contract) live in the command itself — they run on every invocation.
What ships with it
8 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.
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.
- 4d ago First seen · 24 lines · 62 tokens per session scan A bfe850623945
flow-phases is a skill published in the GitHub repository HigorAlves/orc (6 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 435 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
triage
Work-unit triage for GitHub issues. Groups raw issues, fuses each group with the AGENTS.md northstar, and externalizes each routed unit to a substrate record a collaborator session is pointed at.
specs
Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue — "file a ticket for this", "open an issue", "write this up for the backlog", "we should track this", "log this bug", "spec this out as a ticket so we can pick it up later" — i.e.…