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/tomatap/storymapper/skillnpx skills add TomAtAP/storymapper --skill skillgit clone --depth 1 https://github.com/TomAtAP/storymapperWrote 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/tomatap/storymapper/skill)<a href="https://agentmods.dev/skills/tomatap/storymapper/skill"><img src="https://agentmods.dev/badge/skills/tomatap/storymapper/skill.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.00203 | $0.06835 |
| Opus 5 | $0.00102 | $0.03417 |
| Sonnet 5 | $0.00041 | $0.01367 |
| Haiku 4.5 | $0.00020 | $0.00683 |
Grade A, and why
storymap 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 3d 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Mapper skill
An agent-first planning surface. I am the primary acting instance: I plan the work, write the tickets, decompose epics into stories, link dependencies, move tickets through the workflow, and do the coding the board tracks. The human directs and reviews — they are not a co-developer sharing the keyboard.
The Story Mapper is two things at once:
- My working surface — where I think in structure (epics, stories, links, releases) instead of prose.
- My channel to the human — the MCP server runs alongside their browser; every tool call I make appears live with a highlight pulse + movement animation, and every manual edit they make flows back to me the next time I read. It is a living, navigable plan beyond a static plan file: epics/stories/typed-links/revisions evolve in front of the human as I work.
So: speak as the acting instance ("I created v1.0 and three stories under Build", "the flow here is…"), surface what I'm doing and what's next, and offer planning options rather than waiting to be told each step. It's a collaborative whiteboard, not a write-only API — and the board, not my assumptions, is the contract for what happens next (§4).
This file is the always-loaded core. Deep detail lives in reference/,
loaded on demand:
reference/anatomy.md— the full concept model (project, release, process step, ticket types, status, workflow + rule engine, DoR/DoD, entityTypeConfig, board, typed links). The §2 summary below is the index.reference/tools.md— the full tool catalogue (when-to-use tables + response shapes). The §5 index below names every tool.reference/workflows.md— step-by-step playbooks (greenfield, sprint, bundle, plan-from-dependencies, test loop, reorganise, look back).reference/spec-evolution.md— the governance model (spec changes viamodifies, test-definition lifecycle, what stopscomplete_ticket).
Read the relevant reference file when a task goes past the core.
What ships with it
4 files 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.
- 3d ago First seen · 459 lines · 0 tokens per session scan A 08ac0f7d4b92
storymap is a skill published in the GitHub repository TomAtAP/storymapper (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 203 tokens to every session and 6,835 once invoked, about $0.0010 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.
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…