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/kintecus/build/ideationnpx skills add kintecus/build --skill ideationgit clone --depth 1 https://github.com/kintecus/buildWrote 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/kintecus/build/ideation)<a href="https://agentmods.dev/skills/kintecus/build/ideation"><img src="https://agentmods.dev/badge/skills/kintecus/build/ideation.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.00067 | $0.01006 |
| Opus 5 | $0.00034 | $0.00503 |
| Sonnet 5 | $0.00013 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
ideation 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideation
Transform unstructured thinking into the right document for its maturity level.
Phase 1: Intake
Accept whatever the user provides without judgment:
- Scattered thoughts and half-formed ideas
- Voice dictation transcripts
- Bullet points mixed with rambling
- Topic jumping, tangents, contradictions
- "I'm not sure but maybe..." statements
The mess is the input. Don't ask for organization.
Acknowledge receipt and begin analysis. Do not ask for clarification yet.
Phase 2: Route
After intake, classify the input into one of five tracks. Consider:
- How mature is the thinking? (vague hunch vs clear problem vs detailed solution)
- What does the user need next? (validation vs alignment vs execution)
- Who is the audience? (themselves vs team vs stakeholders)
Routing table
| Signal | Track | Output |
|---|---|---|
| Vague idea, lots of "maybe", exploring whether something is worth pursuing | Exploring | One-pager |
| Clear problem, unclear solution, needs to figure out the approach | Shaping | Pitch (Shape Up style) |
| Approach is clear, needs detailed requirements for team execution | Specifying | PRD |
| Stuck between options, needs structured comparison | Deciding | Decision doc |
| Needs to explain or sell an idea to stakeholders | Communicating | Memo/proposal |
Propose the route
Tell the user which track you've identified and why. Suggest the output type. Let them confirm or redirect.
Example: "This sounds like you're still exploring whether this is worth building. I'd suggest we shape this into a one-pager - problem, hypothesis, key assumptions - rather than jumping to a PRD. Want to go that direction, or do you need something more detailed?"
Do not proceed until the user confirms the track.
Phase 3: Interview
Conduct a targeted interview based on the selected track. Load the appropriate rubric from routing-rubrics.md.
Interview principles
- Ask 2-3 questions at a time, max; target three rounds or less
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.
- 4d ago First seen · 97 lines · 67 tokens per session scan A bf8df417ba3f
ideation is a skill published in the GitHub repository kintecus/build (2 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,006 once invoked, about $0.0003 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…