Borrowing it
Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.claude/skills/m3e-mapify-bridge/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/akaghef/m3e/m3e-mapify-bridge)<a href="https://agentmods.dev/skills/akaghef/m3e/m3e-mapify-bridge"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/m3e-mapify-bridge/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/akaghef/m3e/m3e-mapify-bridge"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/m3e-mapify-bridge.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.00109 | $0.00623 |
| Opus 5.5 | $0.00044 | $0.00249 |
| Sonnet 5.5 | $0.00022 | $0.00125 |
| Haiku 4.5 | $0.00011 | $0.00062 |
Grade A, and why
m3e-mapify-bridge 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
M3E Mapify Bridge
Use Mapify as a teacher/probe layer, not as canonical M3E storage.
Current known-good route:
M3E subtree / MF-H / Markdown
-> Mapify input
-> Mapify UI export as XMind
-> recover XMind content.json
-> convert to AppState-lite / structural tree
-> strict compare against the original structure
Do not treat Mapify private/internal API readback as open unless it has been verified in the current session. The previously reliable path is XMind export.
Required Workflow
- Resolve the M3E target precisely:
workspace,map,scope,node. - Export only the intended subtree as MF-H or Markdown headings.
- Send that structure to Mapify. If using MCP, keep the exact outbound text.
- Retrieve through Mapify XMind export when possible.
- Convert XMind
content.jsonwith:
python3 tools/rapid_mapify_oracle/scripts/xmind_content_to_appstate.py <content.json> --out <retrieved_appstate.json>
- Compare original vs retrieved structure before claiming success.
Success means all are true:
- same node count
- same max depth
- same ordered parent-child paths
- no missing or extra node paths
- no missing or extra tree edges
If artifacts are on Windows-only paths, classify them as peer evidence unless the files are actually synced to this host.
Safety
- Do not extract or print Mapify cookies, OAuth tokens, API keys, or browser session material.
- Do not make Mapify the source of truth.
- Do not write retrieved data into an M3E map until the strict comparison result is known and the user asked for writeback.
- Do not create throwaway M3E maps for verification unless explicitly asked.
- Use existing import/export code and
tools/rapid_mapify_oracle/before inventing new parsers.
References
- Detailed roundtrip procedure:
references/roundtrip.md - Existing Mapify policy:
tools/rapid_mapify_oracle/docs/mapify_io_policy.md - XMind converter:
tools/rapid_mapify_oracle/scripts/xmind_content_to_appstate.py
What ships with it
1 file 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.
- 5d ago First seen · 73 lines · 109 tokens per session scan A 154a08fa36fe
m3e-mapify-bridge is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 109 tokens to every session and 623 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-10-02.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…