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 role-generatorgit 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/role-generator)<a href="https://agentmods.dev/skills/solofounder-ai/solofounder/role-generator"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/role-generator/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/role-generator"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/role-generator.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.00032 | $0.02235 |
| Opus 5 | $0.00016 | $0.01118 |
| Sonnet 5 | $0.00006 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
role-generator 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Generator
Overview
The Role Generator takes an approved flow and creates specialist role definitions — not generic agents, but deeply specialized for this specific project and request.
Core principle: A generic "Backend Agent" gives generic advice. A "C# ASP.NET 10 + Entity Framework Core 10 + Azure SQL Backend Specialist" gives advice that's actually useful. Every role is specialized.
When to Use
Invoked by solofounder:flow-composer at two points:
- After flow approval — generate roles for the CURRENT batch of stages only (not all stages if the flow has EXPAND markers)
- After flow expansion — when an EXPAND point is reached and new stages are generated, generate roles for those new stages
- On-demand — during stage execution to generate arbiter roles for conflict resolution
CRITICAL: Only generate roles for stages that exist NOW. If the flow has an EXPAND marker after Stage 2, only generate roles for Stages 1-2. Stages 3+ don't exist yet — their roles will be generated when the flow expands after architecture decisions are made.
The Process
digraph role_generator {
"Approved flow arrives" [shape=doublecircle];
"Existing roles in .solofounder/roles/?" [shape=diamond];
"Load existing roles" [shape=box];
"Read project context" [shape=box];
"Read stack/domain learning" [shape=box];
"Generate role for each specialist" [shape=box];
"Save to .solofounder/roles/" [shape=box];
"Present team to user" [shape=box];
"User approves?" [shape=diamond];
"Adjust roles" [shape=box];
"Begin stage execution" [shape=doublecircle];
"Approved flow arrives" -> "Existing roles in .solofounder/roles/?";
"Existing roles in .solofounder/roles/?" -> "Load existing roles" [label="yes"];
"Existing roles in .solofounder/roles/?" -> "Read project context" [label="no"];
"Load existing roles" -> "Read project context";
"Read project context" -> "Read stack/domain learning";
"Read stack/domain learning" -> "Generate role for each specialist";
"Generate role for each specialist" -> "Save to .solofounder/roles/";
"Save to .solofounder/roles/" -> "Present team to user";
"Present team to user" -> "User approves?";
"User approves?" -> "Adjust roles" [label="no"];
"Adjust roles" -> "Present team to user";
"User approves?" -> "Begin stage execution" [label="yes"];
}
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 · 235 lines · 32 tokens per session scan A 3cea3529e8e2
role-generator is a skill published in the GitHub repository solofounder-ai/solofounder (3 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 2,235 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.
orient
Internal skill for commands. Render the shared orientation snapshot - active task, what's in flight, what's next - tracker-universal. Do not trigger on user conversation; only when a command needs the snapshot.
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…
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.
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.