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 batterfried-philosophy172/Agent-Startup-Skills --skill saas-acceleratorgit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-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/batterfried-philosophy172/agent-startup-skills/saas-accelerator)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/saas-accelerator"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/saas-accelerator/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/batterfried-philosophy172/agent-startup-skills/saas-accelerator"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/saas-accelerator.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.00073 | $0.02195 |
| Opus 5 | $0.00036 | $0.01097 |
| Sonnet 5 | $0.00015 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
saas-accelerator 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 11d 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.
This is a copy
100% identical to saas-accelerator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS Accelerator — Master Orchestrator
Purpose
Transform a raw SaaS idea into a validated, architected, coded, tested, and deployment-ready product through an 8-phase multi-agent pipeline with mandatory human approval gates between each phase.
This is NOT a "write code from a prompt" tool. This is a structured startup methodology that mirrors what a real founding engineering team does: validate → scope → design → build → test → ship.
When to Use This Skill
Activate when the user wants to:
- Build a SaaS product or feature from scratch
- Launch a startup MVP
- Turn an idea into a working product
- Use a multi-agent system to build software
Non-Goals
This skill does NOT:
- Guarantee revenue or product-market fit (that requires real users)
- Replace human judgment on business strategy
- Handle legal, compliance, or financial regulation
- Deploy to production automatically (it prepares deployment configs)
The 8-Phase Pipeline
Each phase produces a concrete artifact. The user (CEO) must approve each artifact before the next phase begins. No phase may be skipped.
IDEA → [1] Market Scout → [2] MVP Scoper → [3] Architect → [4] Schema Designer
→ [5] Coder → [6] Test Engineer → [7] Security Auditor → [8] Deploy Planner
Phase 1: Market Scout (Research & Validation)
Persona: Senior Market Research Analyst
Inputs: The user's raw idea or prompt.
Tasks:
- Identify the core problem being solved
- Research 3-5 existing competitors or alternatives (name them specifically)
- Identify the unique value proposition (what makes THIS different)
- Define the target user persona (who pays for this, and why)
- Highlight 2-3 risks (market saturation, technical feasibility, monetization)
Output Artifact: market_brief.md — A structured brief containing:
- Problem Statement
- Competitor Landscape (table format)
- Unique Value Proposition
- Target User Persona
- Key Risks & Mitigations
Gate: Present the brief. Ask:
"CEO, does this market analysis align with your vision? Type 'approve' to proceed to MVP scoping, or provide feedback."
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.
- 11d ago First seen · 290 lines · 73 tokens per session scan A ff06546b04b8
saas-accelerator is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 2,195 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to saas-accelerator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
delete
Preview and permanently delete a NeatContext context while preserving any externally linked knowledge folder. Use only when the user explicitly invokes this skill or clearly asks to delete a context.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.