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 odarino/haren --skill ideategit clone --depth 1 https://github.com/odarino/harenWrote 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/odarino/haren/ideate)<a href="https://agentmods.dev/skills/odarino/haren/ideate"><img src="https://agentmods.dev/badge/skills/odarino/haren/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/odarino/haren/ideate"><img src="https://agentmods.dev/badge/skills/odarino/haren/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.00020 | $0.01645 |
| Opus 5.5 | $0.00008 | $0.00658 |
| Sonnet 5.5 | $0.00004 | $0.00329 |
| Haiku 4.5 | $0.00002 | $0.00164 |
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 15d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideate
Trigger: When the user presents a raw idea, concept, or "I want to build X" statement — read and follow this skill. Also read the agent definition at
agents/ideator.mdin the haren folder.
Take a raw idea at any maturity level and transform it into a validated, research-backed concept brief. The concept brief becomes a baseline document for the Discover phase (blueprint mode).
When to Use
When the Discover intent router detects a raw idea input — no baseline docs, no repos, and the user provides a statement of intent. This skill is invoked automatically; users do not need to call it directly.
Pipeline
Six stages, always in order. Intensity adapts based on idea maturity.
Stage 1: Intake & Assessment
Accept the user's input and classify idea maturity:
- Nascent: One-liner, vague idea, no context beyond the core concept
- Emerging: Concept with some context — the user knows the problem, audience, or constraints
- Formed: Hypothesis to validate — the user has a clear thesis and needs research to confirm or challenge it
Maturity determines intensity for Stages 2 and 3:
- Nascent → deep research (broad), deep interview (full)
- Emerging → moderate research (targeted gaps), targeted interview (specific gaps)
- Formed → light research (validation-focused), light interview (gap-filling)
Output: Maturity classification with rationale, stored in working memory for later stages.
Stage 2: Research Spikes (automatic, parallel)
Resolve all required research IDs upfront using the resolve-next-id skill (call it once per spike, sequentially, before launching spikes in parallel).
Launch up to 3 research spikes by delegating to the research skill:
| Spike | Research Question | Intensity Guide |
|---|---|---|
| Market | "What is the market landscape for {idea}? Existing solutions, competitors, market size, trends, gaps." | Nascent: broad survey. Emerging: targeted gaps. Formed: validation only. |
| Technical | "What are the technical feasibility considerations for {idea}? Tech options, known pitfalls, prior art." | Nascent: broad survey. Emerging: specific tech questions. Formed: validate chosen approach. |
| Internal | "What relevant prior work, lessons, or reusable assets exist in our projects and memory for {idea}?" | All levels: search memory / knowledge base, past project repos, git history. |
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.
- 15d ago Changed 6bda8adf7963
- 1mo ago First seen · 151 lines · 20 tokens per session scan A 07bfec3a144b
ideate is a skill published in the GitHub repository odarino/haren (11 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 1,645 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…