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.
git 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/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/commands/synaptiai/synapti-marketplace/flow"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/flow.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.00056 | $0.01556 |
| Opus 5.5 | $0.00022 | $0.00622 |
| Sonnet 5.5 | $0.00011 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00156 |
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 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.
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 — 123 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:
references/skill-manifests.md is the authority: it is generated from the loader and drift-tested. Each command also lists its own skills under ## Required Skills.
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
Examples
/flow:start 42→ Skill: flow:start, args: "42"/flow:commit→ Skill: flow:commit/flow:pr→ Skill: flow:pr/flow:review 15→ Skill: flow:review, args: "15"/flow:merge 15→ Skill: flow:merge, args: "15"/flow:resolve 15→ Skill: flow:resolve, args: "15"/flow:release patch→ Skill: flow:release, args: "patch"/flow:debug "TypeError in auth module"→ Skill: flow:debug, args: "TypeError in auth module"/flow:design 42→ Skill: flow:design, args: "42"/flow:brainstorm "caching strategy"→ Skill: flow:brainstorm, args: "caching strategy"/flow:issue "password reset fails for SSO users"→ Skill: flow:issue, args: "password reset fails for SSO users"
Bare /flow (No Arguments)
When invoked without arguments, show help and current status:
- Display available verbs with one-line descriptions
- Quick state queries (read-only):
# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`. Bare `/flow` runs in any CWD,
# including non-repos / offline shells, so gh stderr is suppressed.
printf '%s\n' "### Branch"
printf '%s\n' "BRANCH=$(git branch --show-current 2>/dev/null)"
printf '%s\n' ""
printf '%s\n' "### Assigned Issues"
# Capture gh exit code separately: gh success with no records returns `[]` exit 0;
# gh failure (auth, network, non-repo CWD) returns "" with non-zero exit and jq
# 1.8 on empty input produces NO output and exits 0 — so `|| echo 0` does not
# fire and COUNT stays empty, leaking a bare `ASSIGNED_COUNT=` line.
ASSIGNED_JSON=$(gh issue list --assignee @me --state open --limit 5 --json number,title 2>/dev/null); GH_EXIT=$?
if [ $GH_EXIT -ne 0 ]; then
printf '%s\n' "ASSIGNED_COUNT=0"
printf '%s\n' "STATE=unavailable"
else
ASSIGNED_COUNT=$(printf '%s\n' "$ASSIGNED_JSON" | jq 'length' 2>/dev/null)
[ -z "$ASSIGNED_COUNT" ] && ASSIGNED_COUNT=0
printf '%s\n' "ASSIGNED_COUNT=$ASSIGNED_COUNT"
if [ "$ASSIGNED_COUNT" = "0" ]; then
printf '%s\n' "STATE=empty"
else
printf '%s\n' "$ASSIGNED_JSON" | jq -r '.[] | "ISSUE=\(.number) title=\"\(.title)\""' 2>/dev/null
fi
fi
printf '%s\n' ""
printf '%s\n' "### My PRs"
AUTHORED_JSON=$(gh pr list --author @me --state open --limit 5 --json number,title 2>/dev/null); GH_EXIT=$?
if [ $GH_EXIT -ne 0 ]; then
printf '%s\n' "AUTHORED_COUNT=0"
printf '%s\n' "STATE=unavailable"
else
AUTHORED_COUNT=$(printf '%s\n' "$AUTHORED_JSON" | jq 'length' 2>/dev/null)
[ -z "$AUTHORED_COUNT" ] && AUTHORED_COUNT=0
printf '%s\n' "AUTHORED_COUNT=$AUTHORED_COUNT"
if [ "$AUTHORED_COUNT" = "0" ]; then
printf '%s\n' "STATE=empty"
else
printf '%s\n' "$AUTHORED_JSON" | jq -r '.[] | "PR=\(.number) title=\"\(.title)\""' 2>/dev/null
fi
fi
true
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 9651ba3bb01c
- 1mo ago Changed · -30 lines 303c49e9552c
- 1mo ago Changed 127a20a2b425
- 1mo ago First seen · 153 lines · 56 tokens per session scan A 0a7429900ec5
flow is a command published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 5d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,556 once invoked, about $0.0002 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-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.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
ship
Prepare the current branch to ship, commit messages, semver bump, and a PR description, all for approval.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
repo-week
Weekly activity summary across the repo collection (commits, releases, top churn).
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…