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 melodic-software/claude-code-plugins/plugin install architectureWrote 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/melodic-software/claude-code-plugins/map-flow)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/map-flow"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/map-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/skills/melodic-software/claude-code-plugins/map-flow"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/map-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.00098 | $0.03705 |
| Opus 5.5 | $0.00039 | $0.01482 |
| Sonnet 5.5 | $0.00020 | $0.00741 |
| Haiku 4.5 | $0.00010 | $0.00370 |
Grade A, and why
map-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 yesterday.
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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository context
The current repository is both the CONSUMER, whose convention home declares where artifacts land, and the DEFAULT SUBJECT, whose tracked C# contains the entry point.
Collect with an individual Bash call, one command per call: the project root,
git rev-parse --show-toplevel. Treat a failure (not a repository, git unavailable) as an unknown
value and carry on; ${CLAUDE_PROJECT_DIR} is the resolver's --root either way. The <entry point>
argument is required: a route (with an optional leading HTTP verb), Type.Method, or a method name,
not a second repository.
Purpose
Answer "what happens when this entry point runs" from call sites in the tree. Every hop traces to a line in a tracked file. The scripts collect and render. Do not add a hop the script did not emit, and do not bind a call to a class that merely has a method of the same name.
Resolve home
Read ${CLAUDE_PLUGIN_ROOT}/reference/config.md first. This skill writes into architecture_dir
and reads no dialect key: the picture is always a mermaid sequenceDiagram.
Run bash "${CLAUDE_PLUGIN_ROOT}/lib/resolve-convention-home.sh" --root "${CLAUDE_PROJECT_DIR}" and
follow the exit code; never parse the root instruction file yourself. Exit 0: read
<home>/architecture/README.md for architecture_dir. Exit 1, 2, or 3: no declared home.
In order: --out <dir> wins for this run alone, then a declared topic-doc value, then one
question. architecture_dir has NO default. An undeclared and unconfirmed home, including every
non-interactive run, STOPS and points at /architecture:setup.
This skill never writes the consumer's root instruction file or its topic doc;
/architecture:setup apply owns both.
Build the record
"${CLAUDE_SKILL_DIR}/scripts/collect-flow.sh" \
--repo "<subject-repo>" --entry "<entry point>" --depth N \
--generated-on "<YYYY-MM-DD>" --out "<architecture_dir>/flow.json"
--depth defaults to 5. Keep the ${CLAUDE_SKILL_DIR} anchor;
${CLAUDE_PLUGIN_ROOT}/reference/config.md § Script paths
says why. As of: 2026-10-11. Recheck trigger: that section is renamed or removed, or its
own recheck trigger fires.
What ships with it
5 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.
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.
- yesterday Changed · -3 lines · -5 tokens per session 623a0fa95645
- 3d ago Changed · +1 lines 53988fd89f1e
- 11d ago Changed · +1 lines 1f9cbd028916
- 12d ago Changed · +19 lines a699baf24ba4
- 14d ago Changed · +1 lines 3be3a9225b06
- 16d ago Changed · +55 lines ab159a53b537
- 17d ago First seen · 164 lines · 103 tokens per session scan A 215a026547ee
map-flow is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 3,705 once invoked, about $0.0004 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-29.
Other skills, from other repositories
cascade-type-conversion
For flexible parsing: try multiple type conversions in order, graceful fallback from specific to general types.
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
rust-coding-standards
Rust coding standards, documentation authoring, content workflows, and quality patterns for systemprompt.io development.
visual-design-system
World-class visual design system standards — OKLCH color science, fluid typography, elevation hierarchy, branded asymmetric corners, and dark mode implementation.