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 san-npm/skills-ws --skill marketplace-launchgit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/marketplace-launch)<a href="https://agentmods.dev/skills/san-npm/skills-ws/marketplace-launch"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/marketplace-launch/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/san-npm/skills-ws/marketplace-launch"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/marketplace-launch.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.00083 | $0.06871 |
| Opus 5 | $0.00042 | $0.03436 |
| Sonnet 5 | $0.00017 | $0.01374 |
| Haiku 4.5 | $0.00008 | $0.00687 |
Grade A, and why
marketplace-launch 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace Launch
Launch products across marketplaces and directories for maximum visibility, backlinks, and customer acquisition.
1. Product Hunt Launch Playbook
Pre-Launch (2-4 Weeks Before)
Hunter selection:
- Top hunters get more visibility but are flooded with requests
- Self-hunting is fine now — PH algorithm no longer heavily favors known hunters
- If using a hunter: reach out 3-4 weeks early with a personal pitch, not a template
- Provide them: one-liner, tagline, description, media assets, your availability on launch day
Asset preparation checklist (field limits change — confirm against the live submit form / Product Hunt's launch guide before finalizing):
- Tagline: ~60 characters, benefit-focused (not feature-focused)
- Description: up to ~500 characters — lead with the outcome, then the differentiator
- Thumbnail: 240×240px logo/GIF, under ~3MB, clear on white; this is the icon people see in the feed — make value legible in 3 seconds
- Gallery: 2+ images required, aim for 4-6 at 1270×760px (first image is the most important — treat it as the hero)
- Video: YouTube link only (PH does not host uploads). A 30-90s demo lifts engagement; embed the YouTube URL in the video field
- Interactive demo (optional, 2026): PH supports embedded interactive demos (e.g. via tools like Arcade/Storylane) — strong for letting people try before they leave the page
- Launch tags/topics: pick up to 3 relevant topics. In 2026 the high-traffic dev/SaaS topics include AI, AI Agents, Developer Tools, Productivity, and "vibe coding"-adjacent tags — choose the topic where you can realistically rank, not just the biggest
- Launch URL: use your clean canonical homepage. Do NOT use a shortened or UTM-tagged link in the launch URL field — PH strips/penalizes these and it breaks the redirect. Track attribution via a referrer-based view or a dedicated
/phlanding route instead - Account: launch from a personal maker account. Company/brand accounts as the submitter are not allowed — add the company as the product's maker/team
- Maker comment: draft your first comment (see launch day section)
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 · 455 lines · 83 tokens per session scan A a3696334900e
marketplace-launch is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 5d ago), licensed MIT. It adds 83 tokens to every session and 6,871 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-31.
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…
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…
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…