Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops/plugin install opsWrote 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/lifecycle-innovations-limited/claude-ops/flow)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/flow"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/flow.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.00029 | $0.02684 |
| Opus 5 | $0.00015 | $0.01342 |
| Sonnet 5 | $0.00006 | $0.00537 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
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 8d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams support
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when a
lifecycle stage fans out into parallel, coordinated work (e.g. build + test +
review running together, or a multi-repo ship). This enables:
- Stage agents share context mid-flight (the test agent surfaces a regression → the build agent pivots before review starts)
- You can steer priorities in real time ("land the API change first, then docs")
- Agents report progress as each stage completes, so you sequence the merge
Team setup (only when the flag is enabled, and only for genuinely parallel stages):
TeamCreate("flow-lifecycle")
Agent(team_name="flow-lifecycle", name="stage-build", ...)
Agent(team_name="flow-lifecycle", name="stage-test", ...)
Steer with SendMessage / broadcast; share work via TaskCreate/TaskUpdate.
If the flag is NOT set, fall back to standard fire-and-forget subagents (the default), or just route the stage to its single canonical command inline.
Runtime Context
Before routing, compute where the user is on the lifecycle:
# FLOW_TARGET: the project you are actually working on. Default to the shell's
# cwd, but pass an explicit path when the harness's tool cwd is not the project
# (see the mode-resolution note below).
FLOW_TARGET="${FLOW_TARGET:-$PWD}"
FLOW_STATE=""
for _d in "${CLAUDE_PLUGIN_ROOT:-}" \
"$HOME/Developer/repos/claude-ops/claude-ops" \
"$HOME/external-skills/claude-ops" \
"$HOME/.claude/plugins/marketplaces/ops-marketplace/claude-ops" \
"$HOME/Projects/claude-ops/claude-ops"; do
[ -n "$_d" ] && [ -x "$_d/bin/flow-state" ] && { FLOW_STATE="$_d/bin/flow-state"; break; }
done
[ -n "$FLOW_STATE" ] || { echo "flow: no executable bin/flow-state found" >&2; exit 1; }
"$FLOW_STATE" "$FLOW_TARGET"
Both failures are fail-closed on purpose. If no helper resolves, or the
target path is not a directory, stop and say so — do not route. MODE is what
decides GSD vs gstack, so routing without it silently picks the wrong half of
the lifecycle, which is worse than an error.
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.
- 8d ago First seen · 184 lines · 29 tokens per session scan A a761ba6be329
flow is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (186 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 2,684 once invoked, about $0.0001 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
change-management-planner
Plans organizational change initiatives including technology rollouts, process redesigns, and team restructuring. Maps stakeholders, identifies resistance, designs communication plans, and builds adoption strategies with measurable milestones.
employee-onboarding-designer
Designs structured employee onboarding programs that reduce time-to-productivity and improve retention. Creates day-by-day onboarding plans, training checklists, milestone assessments, and 30/60/90 day success criteria tailored to the role type.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
work-unit-decomposition
Decompose implementation plans into discrete work units with enumerated DoD items, file scope declarations, dependency mapping, and human checkpoint flags.
anti-drift
Hierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.