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/ideatenpx skills add infohata/mind-vault --skill ideategit 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/ideate)<a href="https://agentmods.dev/skills/infohata/mind-vault/ideate"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/ideate.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.00084 | $0.02320 |
| Opus 5 | $0.00042 | $0.01160 |
| Sonnet 5 | $0.00017 | $0.00464 |
| Haiku 4.5 | $0.00008 | $0.00232 |
Grade A, and why
ideate 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ideate
Optional zeroth stage of the sprint workflow, above /idea. Where /idea captures one specific idea the user already has in mind, /ideate discovers a set of candidate improvements the user didn't know they wanted yet. Divergent generation followed by adversarial filtering, producing a menu of strong candidates. The user picks which to promote into actual IDEA files via the existing schema.
This skill does not plan, brainstorm requirements, or execute. It surfaces, critiques, and hands off to /idea for per-candidate capture. Typical trigger: a user between sprints, or starting on a new project area, asking "what should we tackle?" rather than "how do we build X?".
When to use
TRIGGER when:
- user says "what should we build next", "help me find improvements", "let's ideate", "scan the codebase for issues", "what could we clean up", "what's worth tackling", "surface candidate work", "I'm between sprints"
- user is new to a codebase area and wants a landscape of what to improve
- sprint-end retrospective moment when the next-sprint backlog is empty or thin
AGENT_curator's sprint-end promotion sweep surfaces multiple compound candidates and the user wants to triage them as a batch
SKIP when:
- user already has one specific idea → route to
/idea - user has a filled-out IDEA file and wants to flesh it out → route to
/plan(or/brainstorm) - user wants to execute an existing plan → route to
/work - the scope is unclear ("help me think about things") — ask for a bounded area first (a specific app, layer, file-tree scope) before running the scan
Pattern
1. Establish scope
Ideation without a bounded scope produces noise. Before generating candidates, pin down:
- Project / area. Whole project, one Django app, one feature surface, the test suite, the docker setup, the docs tree?
- Timeline. Candidates for this sprint? Next quarter? "Someday"?
- Budget. How many candidates does the user want surfaced — 5? 10? 20? Default to 10.
- Constraints. Anything explicitly off-limits (frozen module, legacy app nobody touches)?
What ships with it
2 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 · 140 lines · 84 tokens per session scan A c75c70bd7e73
ideate is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 84 tokens to every session and 2,320 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…