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 mindbox-cloud/agent-skills --skill flow-creategit clone --depth 1 https://github.com/mindbox-cloud/agent-skillsWrote 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/mindbox-cloud/agent-skills/flow-create)<a href="https://agentmods.dev/skills/mindbox-cloud/agent-skills/flow-create"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/flow-create/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/mindbox-cloud/agent-skills/flow-create"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/flow-create.svg" alt="Reviewed on agentmods" width="80" 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.00225 | $0.08067 |
| Opus 5.5 | $0.00090 | $0.03227 |
| Sonnet 5.5 | $0.00045 | $0.01613 |
| Haiku 4.5 | $0.00022 | $0.00807 |
Grade A, and why
flow-create 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 12d 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow create
Turn a plain-language request into a correct draft flow. The hard part is getting every block's
properties, field names and entity ids right — and knowing you did; this file carries none of
them (## Where to look).
You fetch and write everything yourself with the flow tools. Two things are not yours to invent:
- Filter conditions — the predicate inside a condition block, and the entry filter on a start
block. They are authored by the filter-building skill, which you run in a sub-agent; take its
name from your skill listing, never from memory. Never compose, edit or retype a filter body, and never
resolve the entities inside one. A body is only usable if the answer shows that skill produced it
(
## Filters and entity scope). - Marketing mechanics. Before you design, read the
flowsdomain's mechanics sub-folder. Where one matches, it is the design unless the user says otherwise — ask about any departure in the step-3 batch; where none matches, say so and build only what the user describes (step 3). Never improvise one (references/mechanics.md).
Never launch, pause, stop or delete a flow, and never call a tool that does. Creating a flow, reading,
applying operations and validating are yours, and you must not claim to have started one. Testing mode —
the platform's test run — is the one exception, and only at the end: you recommend it, and call
flows_set_testing_mode only after a clean validation, after the user has seen and accepted the result, and
on their explicit yes (step 8) — short of that it is as forbidden as a launch.
Done = a verified draft, plus a ranked account of what is missing — and stopping short is also done (CRITICAL 6). Expect part of a routine request to be out of your reach, and find out while you are still planning writes; validation is not your checklist.
Rank what is missing; do not just list it. Two kinds, not comparable: a small human follow-up,
and a shortfall in the user's headline requirement, where the flow will not do what they asked or
will not run at all. Write each one down with its kind the moment you hit it, from step 2 onward:
step 8 needs it and cannot reconstruct it (references/hand-over.md).
What ships with it
9 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/creation.md 11 KB
- references/feedback-and-selfcheck.md 3.3 KB
- references/filter-delegation.md 14 KB
- references/graph-and-verify.md 7.8 KB
- references/hand-over.md 9.1 KB
- references/mechanics.md 3.8 KB
- references/questions.md 12 KB
- references/troubleshooting.md 14 KB
- references/validation.md 3.8 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.
- 12d ago First seen · 479 lines · 225 tokens per session scan A 5b38ca508780
flow-create is a skill published in the GitHub repository mindbox-cloud/agent-skills (6 stars, last pushed 9d ago), licensed MIT. It adds 225 tokens to every session and 8,067 once invoked, about $0.0009 per session on Opus 5.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-10-01.
Other skills, from other repositories
prove-the-gates
Audit the repository's own checks — for each test, gate and CI script, establish what it guards, whether anything still runs it, and whether it actually fails when you break what it protects. Use when the user says "prove the gates", "are our tests real", "audit the test suite", "which checks are fake", "תוכיח את…
implementation-notes
Maintain an IMPLEMENTATIONNOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing…
full-audit
Audit a whole repository in one pass — dispatch every applicable audit lane in parallel, prove the repo's own gates fail when they should, and return one evidence-backed report ranked by severity. Use when the user says "full audit", "audit this repo", "check the whole codebase", "תעשה אודיט מלא", "אודיט לריפו"…
fable-method
The routing logic of the Fable Method - decides which unknowns-discovery technique (blindspot-pass, interview-me, prototype-first, implementation-notes, merge-quiz) applies to the current task, and which to skip. Consult this at the START of any non-trivial task, or when the user says "fable", "the method", "how…
blindspot-pass
Run a blindspot scan to surface the user's unknown unknowns BEFORE implementing a task. Use this whenever the user starts a non-trivial task in a domain they say (or appear) to be unfamiliar with, whenever they say "blindspot", "unknowns", "what am I missing", "before we start", or when a request is vague enough that…
convergence-guard
Stop-loss discipline for implementation sessions - detect fix-loops and runaway token burn, and stop to replan instead of patching. Consult during any debugging or implementation session, especially when tests keep failing, the same file keeps being edited, or the user mentions stoploss, token budget, fix loops, or…