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/rasatpetabit/masterplan/masterplan-detectnpx skills add rasatpetabit/masterplan --skill masterplan-detectgit clone --depth 1 https://github.com/rasatpetabit/masterplanWrote 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/rasatpetabit/masterplan/masterplan-detect)<a href="https://agentmods.dev/skills/rasatpetabit/masterplan/masterplan-detect"><img src="https://agentmods.dev/badge/skills/rasatpetabit/masterplan/masterplan-detect.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.00116 | $0.01398 |
| Opus 5 | $0.00058 | $0.00699 |
| Sonnet 5 | $0.00023 | $0.00280 |
| Haiku 4.5 | $0.00012 | $0.00140 |
Grade A, and why
masterplan-detect 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Central agent policy
AUQ, Serena, Hindsight, context-mode, and agent policy is centralized in AGENTS.md (routing resolves from policy/workflow-map.json; fleet policy at /srv/workflows/policy/dispatch.md). This skill must not duplicate or override dispatch rules. User-facing choices must use ask_user_question / AskUserQuestion, never prose questions.
Detecting legacy masterplan bundles for /masterplan import
This skill suggests, it does not act. The user must explicitly run /masterplan import (or, for non-importable artifacts, a fresh full/brainstorm) to act.
/masterplan import is not a generic legacy-document importer. It maps to mp migrate-bundle, which ingests
only a legacy masterplan bundle's state.yml (schema_version 5.x) and re-freezes it into a v8 run. It cannot
convert arbitrary planning markdown (PLAN.md, TODO.md, ROADMAP.md, design/RFC docs, PR task lists). Those have
no import path — the honest suggestion for them is a fresh /masterplan brainstorm seeded from the repo context,
never a claim that import will ingest them.
When to fire
The user is in a git repo and at least one of these is true:
- A legacy masterplan bundle exists at
docs/masterplan/<slug>/state.ymlwhoseschema_versionis 5.x (or predates 5.0, which import will refuse) and there is no matching already-migrated v8 run for the same<slug>.
That is the entire importable surface. The following are not importable, so they do not by themselves warrant an import suggestion:
- A planning-shaped file lives at the repo root or in a common docs directory:
PLAN.md,TODO.md,ROADMAP.md,WORKLOG.md,NOTES.mddocs/plans/*.md,docs/design/*.md,docs/rfcs/*.md,architecture/*.md,specs/*.md
- A pre-v3 masterplan artifact exists under
docs/superpowers/{plans,specs,retros,archived-plans,archived-specs}and there is no matchingdocs/masterplan/<slug>/state.yml. - An open feature branch (not yet merged into the trunk) has descriptive name + commit history that suggests a tracked feature, but no masterplan status file exists for it.
- A draft PR's body contains a task list (
- [ ]/- [x]/ numbered steps).
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 · 90 lines · 116 tokens per session scan A a4bcdb4274af
masterplan-detect is a skill published in the GitHub repository rasatpetabit/masterplan (9 stars, last pushed 4d ago), licensed MIT. It adds 116 tokens to every session and 1,398 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.
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…