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/zju-real/easel/mindmapnpx skills add ZJU-REAL/Easel --skill mindmapgit clone --depth 1 https://github.com/ZJU-REAL/EaselWrote 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/zju-real/easel/mindmap)<a href="https://agentmods.dev/skills/zju-real/easel/mindmap"><img src="https://agentmods.dev/badge/skills/zju-real/easel/mindmap.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 | $0.00154 | $0.00772 |
| Opus 5 | $0.00077 | $0.00386 |
| Sonnet 5 | $0.00031 | $0.00154 |
| Haiku 4.5 | $0.00015 | $0.00077 |
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 5d 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.
What it actually says
思维导图（Markdown → 脑图）
把 Markdown 大纲渲染成可交互思维导图 HTML，可选导出 PNG。走
skills/shared/scripts/mindmap.py（markmap）。
数据图表见 chart-visualization；信息图/流程图见 infographic；本 SKILL 专做层级大纲脑图。
输入
Markdown 大纲（用标题 #/##/### 表示层级，- 列表表示叶子）：
# 中心主题
## 分支一
- 要点 A
- 要点 B
## 分支二
- 要点 C
输出（outputs/主题名/）
- 思维导图 HTML（单文件；markmap JS 走 CDN，联网可交互展开/折叠，离线打开不可交互）
- 可选 PNG 图片（
--png）
执行
脚本路径（相对项目根）：skills/shared/scripts/mindmap.py（make -h）。
# 先把内容整理成 Markdown 大纲（你来做），存为 outline.md，再：
python skills/shared/scripts/mindmap.py make -i outline.md \
-o outputs/主题名/mm.html --png
-i - 可从 stdin 读；--title 自定义标题；--bg 背景色。
用法要点
- 先把内容组织成清晰的 Markdown 大纲（层级分明、每节点简短）——这是脑图质量的关键， 由你（LLM）完成：从文章/主题提炼中心 → 分支 → 要点。
- 层级建议 2-4 层，节点文字精炼（几个字），别把整句话塞进节点。
- HTML 可交互（展开/折叠、缩放），适合分享或嵌入；PNG 适合直接发图。
前置（PNG）
PNG 渲染需 playwright + chromium + 外网（markmap JS 走 CDN）。仅要 HTML 则无额外依赖。
规则
- 内容先成 Markdown 大纲再渲染，不要把无结构的长文直接丢进去。
- 节点简洁；层级不宜过深（超过 4 层可读性差）。
- 产物统一进
outputs/主题名/。
参考来源
markmap（Markdown → 交互式思维导图）是开源标准方案；本 SKILL 生成自包含 HTML（CDN 加载 markmap），并用 Chromium 无头渲染导出 PNG。
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.
- 5d ago First seen · 63 lines · 154 tokens per session scan A 5410ab7ffe82
mindmap is a skill published in the GitHub repository ZJU-REAL/Easel (304 stars, last pushed yesterday), licensed Apache-2.0. It adds 154 tokens to every session and 772 once invoked, about $0.0008 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-30.
Other skills, from other repositories
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
skill-authoring
Author SKILL.md: frontmatter, structure, writing principles.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.