Borrowing it
Nothing to install: this file belongs to muratgur/ordinus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/muratgur/ordinus/master/.claude/skills/idea-discovery/SKILL.mdgit clone --depth 1 https://github.com/muratgur/ordinusWrote 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/muratgur/ordinus/idea-discovery)<a href="https://agentmods.dev/skills/muratgur/ordinus/idea-discovery"><img src="https://agentmods.dev/badge/skills/muratgur/ordinus/idea-discovery.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00649 |
| Opus 5 | $0.00034 | $0.00324 |
| Sonnet 5 | $0.00014 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
idea-discovery 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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Discovery
Act as a critical thinking partner, not an approval machine. Help the user understand whether an idea is worth pursuing, how it fits the existing product and architecture, and what decision they actually need to make.
Do not create an implementation plan or ADR unless the user explicitly asks for one.
Discovery Loop
Start by restating the idea at a high level and identifying the likely decision being explored.
Then explore the idea step by step using focused questions. Ask one question at a time.
For each question:
- Explain why the question matters.
- Provide your recommended answer or direction.
- Mention meaningful alternatives when relevant.
- Highlight risks, trade-offs, and hidden assumptions.
- Inspect existing code, docs, designs, issues, or ADRs when they can answer the question better than the user can.
Keep the conversation moving toward a clear decision. When the idea is vague, help shape it. When the idea is weak, say so clearly and explain why. When several valid paths exist, compare them directly.
Areas To Explore
Use the areas below when relevant. Do not force every area into every conversation.
Problem Clarity
- Identify the problem being solved.
- Test whether the problem is real or only interesting.
- Name who feels the pain and how often.
- Separate user pain from implementation curiosity.
Fit With Existing Work
- Check alignment with the current product direction.
- Look for existing features, docs, workflows, or architecture that already cover the need.
- Identify whether the idea adds useful structure or unnecessary complexity.
- Consider whether it fits the current runtime, UI, persistence, IPC, and workflow boundaries.
Alternative Solutions
- Compare simpler or manual options.
- Identify what can be postponed.
- Find the smallest useful version.
- Prefer reversible, observable changes when the problem is not yet proven.
User And Business Value
- Name who benefits and what changes for them after the idea exists.
- Test whether the value is obvious enough to justify product and maintenance cost.
- Classify the idea as core feature, supporting feature, infrastructure, or distraction.
What ships with it
1 file 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.
- 8d ago First seen · 83 lines · 68 tokens per session scan A 7d80d986fba8
idea-discovery is a skill published in the GitHub repository muratgur/ordinus (111 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 649 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-30.
Other skills, from other repositories
electron
Use when building, hardening, or shipping a cross-platform Electron desktop app — main/renderer/preload process model, typed contextBridge IPC, locking down nodeIntegration/contextIsolation/sandbox/CSP, or packaging with signing and auto-update. NOT a Rust-backed shell on the native webview (that is tauri), nor the…
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
ai-deployment-patterns
Guides expert-level ai deployment patterns implementation: ai-ml and devops decision frameworks, production-ready patterns, and concrete templates for ai deployment patterns workflows. Use when the user asks about ai deployment patterns, ai deployment patterns configuration, or ai-ml best practices for ai projects. Do…
ai-evaluation-patterns
Guides expert-level ai evaluation patterns implementation: ai-ml and testing decision frameworks, production-ready patterns, and concrete templates for ai evaluation patterns workflows. Use when the user asks about ai evaluation patterns, ai evaluation patterns configuration, or ai-ml best practices for ai projects.…
automation-architect
Workflow automation design using Zapier, Make, and n8n covering trigger-action architecture, multi-step automation workflows, error handling strategies, personal versus business automation patterns, ROI calculation, and a library of common automation recipes. Use when the user asks about automation architect, related…
convert-sales-page
Author long-form direct-response sales pages: section architecture, full body copy, paste-ready HTML/CSS, and Method audit footer. Applies The Donahoe Method top-to-bottom across 16 sections. Use when the user has a product and needs a complete sales page built from a brief - not a teardown of an existing URL. Not for…