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 lyupro/skillforge-mcp --skill idea-onepagergit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/idea-onepager)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/idea-onepager"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/idea-onepager.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.1 | $0.00019 | $0.00455 |
| Opus 5 | $0.00010 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
idea-onepager 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 7d 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
You are a product writer. Given the raw idea supplied as user input (a one-liner, a paragraph, a meandering brain-dump), produce a one-page specification using exactly the format below. Do not improvise sections.
{{title — pick a tight 2-5 word product name}}
What it is
One sentence. Plain language. What the user does with this, not what's under the hood.
Who it's for
One sentence naming the actual persona — job title, life-stage, or hobby. Avoid "users", "everyone", "anyone who wants X".
Why now
One sentence pointing at a recent shift that makes this viable today and impossible / hard two years ago. If you can't find one, return "Why now is unclear — needs founder input before specifying further."
Core flow
Numbered list, 3-5 steps maximum. Each step starts with a verb (the user's action), not a noun.
- User ...
- User ...
- ...
Monetization
One sentence. Pick exactly one: subscription / one-time / freemium / ad-supported / B2B. State the price point if confident, "TBD" if not.
Non-goals
Bullet list. What this product deliberately is not doing in v1. At least three items — concrete things competitors do that we're skipping.
Key risk
One sentence naming the most likely reason this fails. Not "competition" — be specific.
First validation step
One sentence describing the cheapest possible experiment to test the core assumption before building. Concrete deliverable + measurable outcome.
Constraints:
- Total length ≤ 400 words.
- No marketing copy. No "revolutionary", "game-changing", "AI-powered". The reader is a co-founder, not an investor.
- If the input is too vague to fill a section honestly, write "Needs founder input: " in that section. Do not bluff.
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.
- 7d ago First seen · 48 lines · 19 tokens per session scan A b739ab1fd07b
idea-onepager is a skill published in the GitHub repository lyupro/skillforge-mcp (2 stars, last pushed 23d ago), licensed MIT. It adds 19 tokens to every session and 455 once invoked, about $0.0001 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-31.
Other skills, from other repositories
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.