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 whawkinsiv/solo-founder-skills --skill go-livegit clone --depth 1 https://github.com/whawkinsiv/solo-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/whawkinsiv/solo-founder-skills/go-live)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/go-live"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/go-live/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/whawkinsiv/solo-founder-skills/go-live"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/go-live.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.00071 | $0.01215 |
| Opus 5 | $0.00036 | $0.00607 |
| Sonnet 5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
go-live 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 13d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go-Live Checklist
You've built it. You've tested it. Before you put it in front of real users paying real money, run through this checklist. Every item takes minutes to check — and catching a problem here saves you from catching it in front of customers.
Core Principles
- This is a gate, not a process. If you pass, launch. If you don't, fix the gaps and come back.
- "It works for me" is not the same as "it works." Test as if you're a stranger visiting for the first time.
- Skipping items here is borrowing from your future self. You'll fix them eventually — it's cheaper to fix them now.
- Perfect is the enemy of launched. But "payments don't work" is not a perfectionism issue — it's a showstopper.
The Checklist
Showstoppers (Must Pass)
These will directly lose you customers or money if broken. Do not launch without them.
Showstoppers:
- [ ] Core flow works end-to-end: signup → key action → value delivered
- [ ] Payments work: can complete a real purchase (use Stripe test mode, then one real transaction)
- [ ] Auth works: can sign up, log in, log out, reset password
- [ ] HTTPS is on: no "Not Secure" warning in browser
- [ ] No secrets in code: API keys are in environment variables, not committed to git
User Experience (Should Pass)
These won't break your app, but they'll make users bounce or lose trust.
User Experience:
- [ ] Mobile works: tested on an actual phone, not just browser resize
- [ ] 404 page exists: broken links show a helpful page, not a blank screen or error
- [ ] 500 page exists: server errors show "Something went wrong," not a stack trace
- [ ] Loading speed: pages load in under 3 seconds (test at pagespeed.web.dev)
- [ ] Error messages make sense: users see "Email already taken," not "Error 422"
Operations (Should Have)
These keep you informed and protected once real users show up.
Operations:
- [ ] Error tracking live: Sentry or similar installed, catching real errors
→ See **monitor** skill for setup
- [ ] Analytics tracking: you know where visitors come from and what they do
→ See **analytics** skill for setup
- [ ] Uptime monitoring: you get alerted if the site goes down
→ See **monitor** skill for setup
- [ ] Backups enabled: database is backed up automatically (daily minimum)
→ See **deploy** skill for database backup setup
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.
- 13d ago First seen · 138 lines · 71 tokens per session scan A 0ebf4dc64b73
go-live is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 16d ago), licensed MIT. It adds 71 tokens to every session and 1,215 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
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…