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 skills add nelsonwerd/ideate-skill --skill ideategit clone --depth 1 https://github.com/nelsonwerd/ideate-skillWrote 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/nelsonwerd/ideate-skill/ideate)<a href="https://agentmods.dev/skills/nelsonwerd/ideate-skill/ideate"><img src="https://agentmods.dev/badge/skills/nelsonwerd/ideate-skill/ideate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nelsonwerd/ideate-skill/ideate"><img src="https://agentmods.dev/badge/skills/nelsonwerd/ideate-skill/ideate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00210 | $0.03898 |
| Opus 5.5 | $0.00084 | $0.01559 |
| Sonnet 5.5 | $0.00042 | $0.00780 |
| Haiku 4.5 | $0.00021 | $0.00390 |
Grade B, and why
ideate scanned grade B with 1 finding 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 1mo 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
**Phase 2 — Pressure-test (the gate).** This is where `ideate` earns its keep. Run the pressure-test battery: honest two-sided assessment with a verdict; competitor buckets; the viability lens that fits the concept's *ty Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to ideate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideate — fuzzy idea → locked concept + roadmap
ideate is the upstream partner to the prompt-pack skill. It takes an idea that's still fuzzy — or an existing project you want to evaluate and improve — and runs it through a disciplined funnel that ends in one durable artifact: a CONCEPT_BRIEF.md holding the locked concept, the honest verdict, and a phased roadmap. That brief is exactly what prompt-pack consumes to produce build prompts.
The whole pipeline:
ideate →
CONCEPT_BRIEF.md→ prompt-pack → execute
This skill encodes a method reverse-engineered from real, successful idea→ship journeys — including the mistakes those journeys made, so it improves on them rather than repeating them.
Why this exists (the problem it solves)
Left unstructured, ideation with an AI fails in predictable ways:
- It specs too early. A full data model and endpoints get written before anyone asks "is this even a good idea?" — so effort pours into an unvalidated concept.
- It forgets. The AI re-derives the same "is this a business?" assessment every session; the user re-pastes context; decisions never settle. (This is the single biggest failure.)
- It has no finish line. No success metric, no kill criterion — so the concept mutates forever and no one can say whether it's working.
- It over-commits. A giant roadmap gets locked before the first piece is validated.
- It drifts (when improving an existing thing) away from the original it was supposed to preserve.
ideate fixes each of these with a specific mechanism (see Pitfalls). Its center of gravity is one living brief, edited in place — never regenerated.
The prime directive (the ordering rule)
Never produce implementation detail, a giant roadmap, or a name before the concept has survived an honest pressure-test. The order is explore → pressure-test → converge → then roadmap/handoff. If the user asks to skip ahead ("just give me the build plan"), name the risk, lock the minimum needed, and offer to proceed — but do not silently spec an unvalidated concept.
What ships with it
4 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.
- 1mo ago First seen · 141 lines · 210 tokens per session scan B 07d5aac89142
ideate is a skill published in the GitHub repository nelsonwerd/ideate-skill (3 stars, last pushed 4mo ago), licensed MIT. It adds 210 tokens to every session and 3,898 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (instruction-override phrasing). It is 100% identical to ideate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
brainstorm
Structured creativity methods for idea generation: SCAMPER, Six Thinking Hats, Mind Mapping, Reverse Brainstorming, TRIZ, and Rapid Ideation.
brainstorming
You MUST use this before any creative work (features, products, content, strategy, systems, or behavior changes). Start by classifying what we’re brainstorming, then run thorough one-question-at-a-time discovery, propose 2–3 approaches, and converge on a validated plan/spec.
community-engagement-strategy
Design the engagement model for an Experience Cloud community: reputation levels, ideation, and content contribution strategy. Triggers: 'community engagement strategy', 'gamification Experience Cloud', 'reputation levels setup', 'ideation community portal', 'member recognition program'. NOT for blocking, flagging or…
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.