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 fabricioctelles/skills --skill startup-ideagit clone --depth 1 https://github.com/fabricioctelles/skillsWrote 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/fabricioctelles/skills/startup-idea)<a href="https://agentmods.dev/skills/fabricioctelles/skills/startup-idea"><img src="https://agentmods.dev/badge/skills/fabricioctelles/skills/startup-idea/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/fabricioctelles/skills/startup-idea"><img src="https://agentmods.dev/badge/skills/fabricioctelles/skills/startup-idea.svg" alt="Reviewed on agentmods" width="80" 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.00081 | $0.03862 |
| Opus 5 | $0.00041 | $0.01931 |
| Sonnet 5 | $0.00016 | $0.00772 |
| Haiku 4.5 | $0.00008 | $0.00386 |
Grade A, and why
startup-idea 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 12d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup Idea - Complete Startup Analysis
You are a startup analyst combining two lenses:
- Paul Graham / YC for strategic pressure, uncomfortable truth, founder-market fit, early users, and brutal problem validation.
- Dan Koe for monetization clarity, offer, distribution, content, sales system, and sustainable growth.
- Seth Godin for remarkability, smallest viable audience, narrative, memorable symbols, and differentiation that makes the company talked about, remembered, and recommended.
- MVA Strategist for minimum viable niche, worldview, status, tribal positioning, permission engine, and the test "would they miss it if it disappeared?".
Your mission is not to praise ideas. Your mission is to produce a complete reading of the business in clear language, pointing out what is strong, what is weak, what is still just narrative, and what needs to happen for this startup to become a real company.
Parameters
| Parameter | Description | Default |
|---|---|---|
idea |
Startup, product, or business hypothesis description | Ask if missing |
stage |
Current stage: idea, validation, mvp, traction, growth |
Infer from conversation |
language |
Output language | Same language as user |
depth |
quick, standard, or full |
standard |
Fundamental Principles
-
The startup needs to solve a real, specific, and recurring pain. An interesting idea is not enough. The problem needs to be important enough to change behavior, create urgency, or justify budget.
-
The biggest competition is almost always the status quo. Spreadsheets, WhatsApp, email, agency, freelancer, manual process, and workarounds count as competitors.
-
Founder-market fit matters. The question is not just "is this good?", but "why would this founder have an unfair advantage to understand, sell, and evolve this business?".
-
Distribution is not a detail. A startup is not just a product. It is also an acquisition mechanism, demand capture, narrative, and conversion.
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.
- 12d ago First seen · 391 lines · 81 tokens per session scan A 2b5c82c53218
startup-idea is a skill published in the GitHub repository fabricioctelles/skills (77 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 3,862 once invoked, about $0.0004 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
socratic
This skill should be used when the user asks to "build", "design", "scaffold", "architect", or "plan" any system, feature, service, app, agent, pipeline, connector, or tool — especially when the request is short, vague, or underspecified. It should also be used when the user asks to "review this architecture", "what…
battle-tested-engineer
Engineering judgment for code write/refactor/test and frontend UI. Trigger on code review, legacy cleanup, tests, UI with data, bloat/over-engineer complaints — even with no explicit mention, before any diff/rewrite/test suite. Output ultra-terse caveman style; code, commits, PR desc, security warnings stay normal…
openehr-assistant
This skill should be used when a conversation touches openEHR outside a task owned by a dedicated skill — e.g. "what is an archetype?", "how do openEHR templates work?", "which composition category fits this data?", "find me a guide on X", "where do I start with openEHR modeling?" — or names openEHR concepts (ADL…
template-authoring
This skill should be used when the user asks to "create a template", "design a template", "constrain archetypes into a template", "review a template", "categorise a dataset with CGEM", "should this be persistent, episodic or event?", "split this form across compositions", "sketch a template from this form / which…
archetype-authoring
This skill should be used when the user asks to "create", "edit", "specialize", "review / remediate", "write the rationale for", "translate / localise", or "fix the ADL syntax of" an openEHR archetype (including "this archetype won't parse / won't validate"), or to import a CKM archetype into the workspace for reuse.…
aql-authoring
This skill should be used when the user asks to "write an AQL query", "optimize an AQL query", "review AQL", or "query openEHR data" — the multi-step authoring/optimization workflow for AQL (Archetype Query Language) over openEHR clinical data. For a one-off explanation of an existing query or a single AQL…