Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sjungling/sjungling-claude-plugins/plugin install 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/commands/sjungling/sjungling-claude-plugins/flow)<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/flow"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/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.00017 | $0.00948 |
| Opus 5 | $0.00009 | $0.00474 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade B, and why
flow scanned grade B with 2 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
kill "$(cat .claude/diagrams/.server.pid)" 2>/dev/null || true Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- The command uses `Bash` (node, kill, mkdir, git) and `Write` (JSON seeding). No `curl` required. How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/flow
Spin up a local React Flow viewer so the user can see — and interactively edit — a diagram described as JSON in .claude/diagrams/<name>.json. The LLM and the browser share the file: you write JSON, the user drags / edits nodes in the browser, and the file updates so you can read their changes on the next turn.
Arguments
$ARGUMENTS — one of:
- (empty) or
<name>→ start the server for diagram<name>(default:diagram). stop→ shut down the running server.- Append
--port Nto override the default port4173.
Behavior
Starting
- Parse
$ARGUMENTS→ diagram<name>(defaultdiagram), optional--port <N>(default4173). - Project root:
git rev-parse --show-toplevel(fall back to cwd if not a git repo). - If
.claude/diagrams/.server.pidexists and that PID is alive (kill -0 <pid>), tell the user the server is already running and print the URL. Do not start a second one. If the PID is stale, delete the file. - Use the Write tool to ensure
.claude/diagrams/<name>.jsonexists. If missing, seed it with{"nodes": [], "edges": []}. If the user described a diagram in this conversation, write an initial graph (nodes + edges) to that file before launching so the viewer opens populated. - Launch the server in the background via Bash:
FLOW_PORT=<port> FLOW_PROJECT_ROOT=<project-root> FLOW_DIAGRAM=<name> \ nohup node "${CLAUDE_PLUGIN_ROOT}/server/server.mjs" \ > .claude/diagrams/.server.log 2>&1 & disown - Print the URL (
http://localhost:<port>) and the diagram file path. Tell the user: "Say done (or run/flow:flow stop) when you're finished and I'll tear it down."
Stopping
- Read PID from
.claude/diagrams/.server.pid. - Send SIGTERM — the server traps it and exits cleanly:
kill "$(cat .claude/diagrams/.server.pid)" 2>/dev/null || true rm -f .claude/diagrams/.server.pid - Confirm shutdown to the user.
Graph JSON shape
Native React Flow. Nodes default to a custom editable type if type is omitted:
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.
- 7d ago First seen · 80 lines · 17 tokens per session scan B 8e38c406adf6
flow is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 24d ago), licensed MIT. It adds 17 tokens to every session and 948 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.