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/0xbeycan/genesis/ideatenpx skills add 0xBeycan/genesis --skill ideategit clone --depth 1 https://github.com/0xBeycan/genesisWrote 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/0xbeycan/genesis/ideate)<a href="https://agentmods.dev/skills/0xbeycan/genesis/ideate"><img src="https://agentmods.dev/badge/skills/0xbeycan/genesis/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.00100 | $0.00524 |
| Opus 5 | $0.00050 | $0.00262 |
| Sonnet 5 | $0.00020 | $0.00105 |
| Haiku 4.5 | $0.00010 | $0.00052 |
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 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.
What it actually says
Ideate — diverge before you converge
An agent's default failure is that the first workable idea wins. This skill is the antidote: a short, deliberate divergence step before a commitment — never instead of one.
When to use
Decisions with real design freedom: a product or feature angle, a name, a design-language direction, an architecture fork with several viable shapes, a debugging dead-end. Also whenever the user asks for alternatives.
When not to use: implementation style (boring wins — ponytail),
decisions already constrained to one viable shape, reversible trivia.
Steps
- Fix the constraints first. What MUST hold (from
AGENTS.md, the vision, the budget)? Constraints are not options — write them down. - Generate 3–5 genuinely different options — different shapes, not variants of one; include one deliberate wildcard from outside the obvious pattern. Search the web if the space is unfamiliar.
- Score against the constraints and goals — one line per option, honest costs included.
- Converge to ONE. Say why it wins, in a sentence.
- Record the rejects: a
docs/memory/decisions.mdline; an ADR when the fork was real (write-adr). Rejected alternatives are the highest-signal part of the record.
Notes
- Division of labor:
clean-code= the shape of code ·ponytail= the amount of code ·ideate= the option space before the commitment. They chain, never clash: ideate picks the what; ponytail minimizes the how. - Diverge on the WHAT, stay boring on the HOW.
- Time-boxed: this is a step, not a session. If the options don't meaningfully differ, say so and move on — forced variety is noise.
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 · 43 lines · 100 tokens per session scan A 51b68e7d2d43
ideate is a skill published in the GitHub repository 0xBeycan/genesis (11 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 524 once invoked, about $0.0005 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-30.
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…