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 ognjengt/founder-skills --skill product-hunt-launch-plangit clone --depth 1 https://github.com/ognjengt/founder-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/ognjengt/founder-skills/product-hunt-launch-plan)<a href="https://agentmods.dev/skills/ognjengt/founder-skills/product-hunt-launch-plan"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/product-hunt-launch-plan/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/ognjengt/founder-skills/product-hunt-launch-plan"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/product-hunt-launch-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00017 | $0.02266 |
| Opus 5 | $0.00009 | $0.01133 |
| Sonnet 5 | $0.00003 | $0.00453 |
| Haiku 4.5 | $0.00002 | $0.00227 |
Grade A, and why
product-hunt-launch-plan 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Hunt Launch Plan
Purpose
Generate a comprehensive, personalized Product Hunt launch plan with actionable steps from A-Z to help the user rank #1 Product of the Day.
Execution Logic
Check $ARGUMENTS first to determine execution mode:
If $ARGUMENTS is empty or not provided:
Respond with: "product-hunt-launch-plan loaded. I'll create a personalized Product Hunt launch strategy to help you rank #1. Let me gather some information about your product first."
Then proceed to the Discovery Questions phase.
If $ARGUMENTS contains content:
Use the provided content as initial context, but still proceed through Discovery Questions to fill any gaps.
Task Execution
When user engages with this skill:
1. MANDATORY: Read Reference Files FIRST
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read the reference file:
Read: ./references/ultimate_product_hunt_launch_guide.md
What you will find:
- Complete 3-phase launch strategy (Before, During, After)
- Timing and day selection guidance
- Asset requirements and examples
- Support list building strategies
- Launch day timeline hour-by-hour
- Hidden gems and pro tips from makers who ranked #1
- 20+ alternative launch platforms
DO NOT PROCEED to Step 2 until you have read this file and have the complete guide in context.
2. Check for Business Context
Check if FOUNDER_CONTEXT.md exists in the project root.
- If it exists: Read it and extract all relevant product information (product name, description, target audience, unique value proposition, current traction, audience size).
- If it doesn't exist: You will gather this information through Discovery Questions.
3. Discovery Questions (MANDATORY)
Ask up to 10 targeted questions to personalize the launch plan.
Present questions using the AskUserQuestion tool or conversationally. Gather:
- Product Basics
- What is your product name and one-line description?
- What problem does it solve and for whom?
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 · 331 lines · 17 tokens per session scan A 965764310904
product-hunt-launch-plan is a skill published in the GitHub repository ognjengt/founder-skills (302 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 2,266 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…