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/juxt/claude-plugins/mindmapnpx skills add juxt/claude-plugins --skill mindmapgit clone --depth 1 https://github.com/juxt/claude-pluginsWhat 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.00118 | $0.02159 |
| Opus 5 | $0.00059 | $0.01079 |
| Sonnet 5 | $0.00024 | $0.00432 |
| Haiku 4.5 | $0.00012 | $0.00216 |
Grade A, and why
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chalk Mindmaps — Structuring What the Reader Must Follow
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
chalk:voice covers the register and the line-format rule. Load both.
The default
Anything the reader has to follow MUST default to a mindmap: nested bullets forming a tree. A sequence of events, a multi-step rationale, a set of conditions, a decision and its grounds.
Prose MUST be a deliberate exception, never a fallback — reserve it for a short causal argument where the connectives ("because", "so", "but only when") carry the meaning and the chain is only two or three links long.
The tree is a support structure
Every parent node MUST be a claim its direct children back up.
- Read downwards it's a summary that expands on demand — the reader stops at whatever depth answers their question.
- Read upwards it's an argument If each child holds, and the children are enough, the parent holds.
- If the relation is serves rather than supports, you're writing a goal tree
Load
chalk:goal-tree, which has its own completeness test.
An arbitrary bullet list is not a mindmap. The test: pick any node and ask whether its children back it up. If they're merely related to it, you've written a flat list with indentation, the reader gets no argument out of it, and it MUST be restructured.
Subject lines carry the reasoning
Reading only the top line of each bullet MUST be enough to follow the whole argument. A paragraph underneath is elaboration — always an optional read, and it MUST NOT be load-bearing. If the point only lands once the reader reaches the third sentence of the elaboration, the subject line has failed and the bullet needs rewriting, not expanding.
- One checkpoint per bullet. Each bullet is a place the reader stops, confirms they've followed, and moves on.
- Bold the load-bearing words. The tree should be graspable from the bolded phrases alone, before a word of the surrounding prose is read.
- Nest for sub-points, but stay shallow — about two levels. A third level of indentation is usually its own wall, so promote it or flatten it.
- Cut hard.
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 · 162 lines · 118 tokens per session scan A 6c3188a2a9c2
mindmap is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 118 tokens to every session and 2,159 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…