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 commands/synaptiai/synapti-marketplace/flowgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/commands/synaptiai/synapti-marketplace/flow)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/flow"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/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.00056 | $0.01821 |
| Opus 5 | $0.00028 | $0.00911 |
| Sonnet 5 | $0.00011 | $0.00364 |
| Haiku 4.5 | $0.00006 | $0.00182 |
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 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.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow: Skill-Driven Workflow
Universal dispatcher for the flow plugin. Parses intent from $ARGUMENTS and routes to the appropriate sub-command with required skills.
Required Skills
None — dispatcher only. Sub-commands declare their own Required Skills (see Skill Manifests below).
Skill Manifests
Each verb requires specific domain skills. The dispatcher invokes these deterministically:
| Verb | Required Skills | Command |
|---|---|---|
| start | branch-and-task-management, change-classification, capability-discovery | /flow:start |
| commit | change-classification, convention-enforcement | /flow:commit |
| pr | pr-lifecycle, code-review-methodology, capability-discovery | /flow:pr |
| review | code-review-methodology | /flow:review |
| address | feedback-resolution, change-classification, capability-discovery | /flow:address |
| merge | merge-and-release | /flow:merge |
| resolve | merge-conflict-resolution, capability-discovery | /flow:resolve |
| release | merge-and-release | /flow:release |
| status | (none — read-only) | /flow:status |
| learn | (none — analysis only) | /flow:learn |
| setup | capability-discovery | /flow:setup |
| explain | (none — read-only) | /flow:explain |
| debug | debugging-patterns, change-classification | /flow:debug |
| design | architecture-patterns, capability-discovery | /flow:design |
| brainstorm | brainstorming, capability-discovery | /flow:brainstorm |
| issue | issue-crafting | /flow:issue |
Routing Logic
Parse $ARGUMENTS to extract verb and target:
- Extract verb: First word of arguments (start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue)
- Extract target: Remaining arguments (issue number, PR number, version type, etc.)
- Route: Invoke the corresponding sub-command via Skill tool with the target as arguments
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 · 153 lines · 56 tokens per session scan A 0a7429900ec5
flow is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,821 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 commands, from other repositories
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
update_version
git tag "thetag"，填入对应的tag 修改static/config.yml中的version的值。 git add并git commit -m "update: version to xxx".
ship
Use after audit returns Verdict PASS. Atomic git commit + tag + ledger update. Single-writer; cannot fan-out.
push
Commit, push, and post a progress comment using session context or branch detection.
create-worktree
Follow these steps to create a git worktree.