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/1a7432/loreweaver/svg-mapmakernpx skills add 1A7432/loreweaver --skill svg-mapmakergit clone --depth 1 https://github.com/1A7432/loreweaverWrote 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/1a7432/loreweaver/svg-mapmaker)<a href="https://agentmods.dev/skills/1a7432/loreweaver/svg-mapmaker"><img src="https://agentmods.dev/badge/skills/1a7432/loreweaver/svg-mapmaker.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.00037 | $0.00783 |
| Opus 5 | $0.00018 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
SVG mapmaker 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 4d 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
SVG mapmaker
Use draw_svg_map when a compact visual structure would help the table understand space,
routes, room hierarchy, or named locations. Good moments include:
- the party enters a new building, dungeon level, ship deck, town district, or investigation board
- players ask how rooms connect or which places are above/below/inside others
- a module has several named scenes and you need a player-safe overview
- you want a handout that shows only discovered or player-visible location names
Do not include keeper-only secrets, hidden rooms, trap truths, culprit identities, unrevealed clue solutions, or private NPC motives. A map is a handout; everything drawn on it is player-visible.
Call draw_svg_map with:
title: the map titlelayout:"hierarchy"for nested/flow structures,"grid"for rooms/floor-like layouts, or"spatial"when you can give rough north/east/size hintsareas_json: a JSON list of area objects
Area objects may contain:
id: short stable id, used byparentandlinksname: label shown on the mapparent: id of the containing/previous areadescription: short player-visible subtitlelinks: list of ids connected to this areapos: forlayout:"spatial", a rough grid coordinate[gx, gy]where north is smalleryand east is largerx(0-11, floats allowed)size: forlayout:"spatial", a rough grid size[w, h]where important rooms can be larger
Example:
[
{"id":"manse","name":"Blackwood Manse","description":"front hall"},
{"id":"library","name":"Library","parent":"manse","description":"locked cabinets"},
{"id":"cellar","name":"Cellar","parent":"manse","description":"cold stone stairs"},
{"id":"tunnel","name":"Old Tunnel","parent":"cellar","description":"bricked arch", "links":["garden"]}
]
Spatial example:
[
{"id":"stairs","name":"Cellar Stairs","description":"from kitchen","pos":[5,0],"size":[2,1]},
{"id":"storage","name":"Storage Room","description":"barrels and sacks","pos":[2,3],"size":[3,2],"links":["stairs"]},
{"id":"cistern","name":"Old Cistern","description":"echoing water","pos":[8,4],"size":[3,2],"links":["storage"]},
{"id":"sealed","name":"Sealed Door","description":"iron-banded","pos":[8,7],"size":[2,1],"links":["cistern"]}
]
Use layout:"spatial" only for player-safe rough layouts. The coordinates are direction and
relative size hints, not exact architectural measurements.
After the tool sends the map, briefly orient the players to what is visible on it and continue the scene. Do not narrate the SVG markup itself.
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.
- 4d ago First seen · 73 lines · 37 tokens per session scan A cb557ef463e9
SVG mapmaker is a skill published in the GitHub repository 1A7432/loreweaver (49 stars, last pushed 2d ago), licensed MIT. It adds 37 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…