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/infohata/mind-vault/plannpx skills add infohata/mind-vault --skill plangit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/plan)<a href="https://agentmods.dev/skills/infohata/mind-vault/plan"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/plan.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.00089 | $0.03733 |
| Opus 5 | $0.00044 | $0.01867 |
| Sonnet 5 | $0.00018 | $0.00747 |
| Haiku 4.5 | $0.00009 | $0.00373 |
Grade A, and why
plan 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan
Second stage of the five-stage sprint workflow (idea → brainstorm/plan → work → review → compound). Turns an atomic IDEA file or a rough feature description into a durable plan that an agent — or a human — can execute from without re-inventing product behavior, scope boundaries, or test scenarios.
This skill merges the brainstorm + plan stages from CE. When input is already specific (a filled-out IDEA file, a bug report with clear repro), the skill skips straight to plan authoring. When input is thin (a one-line description, an IDEA stub), a thin-input bootstrap fires — the interactive brainstorm front-end — before the plan is written. Brainstorming is a mode, not a separate skill. /brainstorm is an alias for /plan.
This skill does not write code, run tests, or modify project source. It does, however, author the plan artifact and — per RULE_ideas-location-status and step 6 below — trigger the single git mv that moves the source IDEA file from docs/ideas/ into its docs/archive/YYYY-MM-idea-NNN-<slug>/ dir. The plan artifact itself lands in that same archive dir (emitted by step 7). Execution belongs in /work (the next stage).
When to use
TRIGGER when:
- user says "plan this", "write a tech plan", "plan the implementation", "how should we build X", "break this down", "what's the approach for Y", "let's brainstorm X", "help me think through X", "deepen the plan"
- user references an existing IDEA file by slug (
/plan sprint-workflow) or path - an IDEA file was just created by
/ideaand the natural next step is to turn it into a plan - the user provides a bug report, a feature idea, or a rough description that would benefit from structured decomposition before execution
SKIP when:
- the work is a one-off trivial fix (typo, one-line bugfix) that a plan would over-engineer
- the user wants to start coding immediately on something well-understood — route to
/workdirectly - the user is still exploring "what to build" at a portfolio level with no single target in mind — route to
/idea(or multiple/ideainvocations) to surface candidates first
What ships with it
6 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.
- 5d ago First seen · 187 lines · 89 tokens per session scan A 4b5cc114e394
plan is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 3,733 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…