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 solofounder-ai/solofounder --skill using-solofoundergit clone --depth 1 https://github.com/solofounder-ai/solofounderWrote 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/solofounder-ai/solofounder/using-solofounder)<a href="https://agentmods.dev/skills/solofounder-ai/solofounder/using-solofounder"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/using-solofounder/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/solofounder-ai/solofounder/using-solofounder"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/using-solofounder.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.00036 | $0.00918 |
| Opus 5 | $0.00018 | $0.00459 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
using-solofounder 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 10d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SoloFounder
Overview
SoloFounder is your AI virtual team. You give any request — building software, planning marketing, reviewing contracts, designing operations — and the system dynamically composes the right team and workflow to execute it.
Nothing is hardcoded. Flows, stages, and specialist roles are generated per-request.
How It Works
- Flow Composer analyzes your request, designs the optimal sequence of stages
- Role Generator creates exactly the specialist roles this flow needs
- Stages execute with specialists participating at each gate
- Conversation Analyst reviews everything post-completion, updates cross-project learning
The Five Iron Laws
Every agent, every stage, every role is governed by these laws:
1. NO FALLBACKS. NO SILENT FAILURES. NO TEMP SOLUTIONS.
2. ONE CORRECT PATH. If it fails, STOP.
3. EVERY EXCEPTION IS ACTIONABLE.
4. IMPLEMENTATION COSTS NOTHING.
5. EVERYTHING IS REVIEWED AND VERIFIED.
Load solofounder:exception-enforcement for the full enforcement guide.
System Architecture
Static (battle-tested, always available):
Meta-skills:
solofounder:flow-composer— Generate flow from any requestsolofounder:role-generator— Generate specialist rolessolofounder:conversation-analysis— Post-completion learning
Capabilities (tools/disciplines stages can use):
solofounder:tdd-methodology— RED-GREEN-REFACTOR enforcementsolofounder:systematic-debugging— 4-phase root cause investigationsolofounder:verification— Evidence before claimssolofounder:exception-enforcement— Iron Laws applicationsolofounder:mockup-server— Visual preview, multi-variant votingsolofounder:live-research— Verify tech recommendations with live docs before recommending
Dynamic (generated per-request):
- Flow definition (
.solofounder/flow.md) - Specialist roles (
.solofounder/roles/) - Stage content, deliverables, and outcomes
On Session Start
- Load the Five Iron Laws into context
- Read
~/.solofounder/learning/insights.mdif it exists (cross-project learning) - Read
.solofounder/roles/if this project has prior roles - Read
.solofounder/flow.mdif this project has a prior flow - Hand off to
solofounder:flow-composer
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.
- 10d ago First seen · 106 lines · 36 tokens per session scan A 263d68a6956b
using-solofounder is a skill published in the GitHub repository solofounder-ai/solofounder (3 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 918 once invoked, about $0.0002 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
codex
Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
x-multi-llm-align
A review process in which two sub-agents examine an API, data format, event schema, or workflow from their separate implementation perspectives. The user passes documents and feedback between them over multiple rounds.
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…