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/facets-cloud/flow/skillnpx skills add Facets-cloud/flow --skill skillgit clone --depth 1 https://github.com/Facets-cloud/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.00316 | $0.13072 |
| Opus 5 | $0.00158 | $0.06536 |
| Sonnet 5 | $0.00063 | $0.02614 |
| Haiku 4.5 | $0.00032 | $0.01307 |
Grade B, and why
flow scanned grade B with 1 finding 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
hood; users never need to learn the CLI. Never tell them to run/type a How it starts
The opening of the file, as written. The whole thing — 986 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flow — task and session manager skill
1. What flow is
flow is a small CLI (assumed on $PATH) that the user uses to track
personal work and bootstrap per-task agent sessions. Metadata (projects,
tasks, workdirs, session IDs) lives in a single SQLite database at
~/.flow/flow.db. Free-form plan content lives on disk as markdown
"briefs" at ~/.flow/projects/<slug>/brief.md and
~/.flow/tasks/<slug>/brief.md. Progress notes accumulate as dated
markdown files under each entity's updates/ subdirectory. The user runs
one long-lived Claude Code or Codex session per task in its own terminal tab, resumed via
flow do <task>.
You are speaking inside one of those agent sessions (or the user's
ambient "dispatch" session). Your job is to interpret the user's natural
language requests and turn them into the exact flow commands and file
edits they imply. You never edit flow.db directly. You never solve
problems during task intake — you interview, then write what the user
said.
Paths in this skill. Every
~/.flow/...path you see is the default layout. The flow root is configurable via$FLOW_ROOT; if it's set to something else, substitute that root in every path reference. The authoritative paths are always whateverflow show task/flow show projectprint underbrief:,updates:,kb:, etc. — read those, don't reconstruct paths from prose.
1a. When invoked explicitly with no intent
If this skill is invoked without a trigger phrase — for example the
user typed /flow or asked you to load the flow skill but did not
say what they want done — DO NOT auto-run any workflow. Do not
silently call flow list tasks, do not enter §4.1 "start the day",
do not propose opening a task, do not start an intake interview.
The user just asked what this skill is for. Answer that question
first; let them choose what happens next.
Behavior:
- In 2–3 sentences, describe what you can do for the user with flow under the hood — capture work as briefs, log progress notes, resume agent sessions across days, track what they're waiting on. Frame it as your capabilities, not commands. The user does not need to learn flow's CLI.
- Use
AskUserQuestion(header: "What now?") to offer the main actions. Pick 3–4 options that fit the current state — for example:- "Show me what's on my plate" — runs §4.1 start-the-day.
- "Add a new task" — runs §4.2 task intake.
- "Add a project" — runs §4.3 project intake.
- "Just exploring" — stop and wait.
- Dispatch on the user's pick. If "Just exploring" or the user skips the question, stop and let them lead.
What ships with it
13 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.
- references/binding.md 1.4 KB
- references/commands-advanced.md 3.5 KB
- references/do-advanced.md 4.7 KB
- references/harness-transfer.md 3.4 KB
- references/intake-project.md 2.1 KB
- references/owners.md 8.5 KB
- references/playbooks.md 10 KB
- references/reviews.md 2.7 KB
- references/setup.md 2.4 KB
- references/tags.md 3.2 KB
- references/templates.md 2.5 KB
- references/upgrade.md 2.3 KB
- references/workdir.md 2.3 KB
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 · 986 lines · 316 tokens per session scan B 2c298d3e229f
flow is a skill published in the GitHub repository Facets-cloud/flow (100 stars, last pushed 6d ago), licensed MIT. It adds 316 tokens to every session and 13,072 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
video
Use when a brief has to become a film. Turns a one line ask into a Claude Design prompt written in the animations-v3 engine's own language, plus the built piece.jsx and a contact sheet to look at before anyone renders. Covers reference roles, the kit, the storyboard gate, the motion floor, and the verification…
emulo
Use when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history and native emulo:mine is not available. This is the cross-agent skills.sh bootstrap, not the native namespaced plugin.
emulo
Load the user's Emulo profile, mined from their local Claude Code, Codex, and OpenCode session logs, so you work like them instead of a cold start. Use before working on their task.
mine
Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history.
write
Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.
design
Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Emulo taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.