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 skills/forgeyclap/claude-forge/forge-mindmapnpx skills add ForgeyClap/claude-forge --skill forge-mindmapgit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWhat 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 | $0.00044 | $0.00783 |
| Opus 5 | $0.00022 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
forge-mindmap 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Mind Map (WP4)
A Forge mind map is a small node/edge graph — a root idea with branches and leaves — that the Lead generates to visualize a plan, an architecture, or a mission decomposition. It is built and stored by .claude/forge-bin/forge-mindmap.cjs, a zero-dependency writer that stores the structured JSON (and optional Mermaid/markdown sidecars) under .claude/forge-mindmaps/.
When the Lead generates one
- To visualize a plan, architecture, or mission decomposition once it has real branching structure (a root idea with several sub-areas) — not for a flat 2-3 item list where prose is clearer.
- Typically right after a Master Plan or Deep Learn Mode pass, so the map reflects real decisions already made, not a guess.
- Not needed for a trivial, single-path task.
How
- Write the structure as an indented plain-text outline (2-space or tab indent = depth; the first line is the root):
Mission Control Phase 2 WP4 Mind Map Writer (forge-mindmap.cjs) Radial lens (dashboard) WP5 Next Work Package - Build + store it:
node .claude/forge-bin/forge-mindmap.cjs from-outline '<outline-text>' <map_id> --write --run <run_id> --mermaid- Omit
--writeto preview the parsed{nodes, edges}JSON without persisting anything. --mermaidalso writes a<map_id>.mmdMermaid sidecar (graph TD, guarded — never crashes on odd input).--run <run_id>logsmindmap_generatedto that run's dashboard events — only fires once the map was actually written.- Already have a built
{map_id, title?, nodes, edges}object instead of an outline? Usewritedirectly:node .claude/forge-bin/forge-mindmap.cjs write '<map-json>' --write --run <run_id>.
- Omit
What it produces
.claude/forge-mindmaps/<map_id>.json (the stored {map_id, title, nodes, edges, _generated}), optionally <map_id>.mmd (Mermaid) and <map_id>.md (nested outline), and an appended row in .claude/forge-mindmaps/index.jsonl. The dashboard's MIND MAP lens reads the latest stored map read-only and renders it as a root-centered radial graph (root at the center, branches/leaves on rings by depth, no node overlap).
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 · 40 lines · 44 tokens per session scan A 9069cad8861e
forge-mindmap is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 44 tokens to every session and 783 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
dev-pain-finder
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where developer frustration is high and…
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.