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 on-deck-society/love-stack --skill pre-launch-auditgit clone --depth 1 https://github.com/on-deck-society/love-stackWrote 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/on-deck-society/love-stack/pre-launch-audit)<a href="https://agentmods.dev/skills/on-deck-society/love-stack/pre-launch-audit"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/pre-launch-audit/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/on-deck-society/love-stack/pre-launch-audit"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/pre-launch-audit.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.00024 | $0.00538 |
| Opus 5.5 | $0.00010 | $0.00215 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
pre-launch-audit 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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Launch Audit
When activated, perform a structured 10-point audit of the user's codebase and report findings.
The 10 Checks
-
Authorization: Review auth middleware, protected routes, and RLS policies. Flag any endpoint that handles user data without auth verification.
-
Input validation and sanitization: Check form handlers, API routes, and database writes for validation. Flag any endpoint that accepts user input without a validation schema (Zod, Yup, or equivalent).
-
CORS policy: Inspect CORS configuration. Flag wildcard origins in production code.
-
Rate limiting on API endpoints: Search for rate limiter middleware. Flag endpoints with no rate limiting, especially auth and public-facing endpoints.
-
Password reset link expirations: If password reset exists, verify tokens expire within a reasonable window (under 1 hour recommended). Flag non-expiring or long-lived tokens.
-
Error handling: Scan catch blocks and error boundaries. Flag any place where raw stack traces, SQL errors, or internal paths could leak to the client.
-
Database indexing: Check schema and migration files for indexes on frequently queried columns (foreign keys, email fields, timestamps used in ORDER BY).
-
Logging: Verify structured logging is in place for auth events, payment events, and errors. Flag console.log in production code paths.
-
Alerts and monitoring: Check for error tracking (Sentry, LogRocket, etc.) and health checks. Flag if none are configured.
-
Rollback strategy: Verify deployment configuration supports rollback. Check for migration rollback scripts, feature flags, or blue-green deploy configuration.
Output Format
Produce a markdown report with:
- Pass/Fail/Partial status per check
- Specific file and line references for every flagged item
- Severity label (Critical, High, Medium, Low)
- One-line recommendation per finding
- Summary at top: "X of 10 passed, Y critical issues, Z high-severity issues"
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.
- 1mo ago First seen · 47 lines · 24 tokens per session scan A a9730127447b
pre-launch-audit is a skill published in the GitHub repository on-deck-society/love-stack (5 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 538 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…