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 Facets-cloud/flow --skill skillgit clone --depth 1 https://github.com/Facets-cloud/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/facets-cloud/flow/skill)<a href="https://agentmods.dev/skills/facets-cloud/flow/skill"><img src="https://agentmods.dev/badge/skills/facets-cloud/flow/skill/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/facets-cloud/flow/skill"><img src="https://agentmods.dev/badge/skills/facets-cloud/flow/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 11 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 157 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 213 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 455 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 455 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 509 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 587 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 588 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Prompt Injection · line 837 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
- medium Rogue Agent · line 841 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- low Excessive Agency · line 7 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00316 | $0.13732 |
| Opus 5.5 | $0.00126 | $0.05493 |
| Sonnet 5.5 | $0.00063 | $0.02746 |
| Haiku 4.5 | $0.00032 | $0.01373 |
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 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.
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 — 1,035 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
14 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/messaging.md 8.4 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.
- 1mo ago Changed · +9 lines 8075eca48c30
- 1mo ago Changed · +40 lines c2a88a564d22
- 1mo ago First seen · 986 lines · 316 tokens per session scan B 2c298d3e229f
flow is a skill published in the GitHub repository Facets-cloud/flow (101 stars, last pushed 8d ago), licensed MIT. It adds 316 tokens to every session and 13,732 once invoked, about $0.0013 per session on Opus 5.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
handoff
A handoff skill that records the current work and the exact state needed for another coding session to continue. It writes this state to HANDOFF.md and can also share it through a project issue or collaboration tool.
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
resume
Pick up where you left off. Restores context and suggests next action.
continue
Execute the next logical step automatically. No prompts, no decisions — just do it.
note
Zero-friction idea capture. Append, list, or promote notes to todos.
session-heartbeat
Use this skill when the user asks "where are we", "status check", "health check", "checkpoint", "what have we done", or any progress review of the current session. Also use when the user wants to switch tasks, drop current work for something urgent, pause to review scope, or says the context/session is getting long.…