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 fortunto2/solo-factory --skill swarmgit clone --depth 1 https://github.com/fortunto2/solo-factoryWrote 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/fortunto2/solo-factory/swarm)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/swarm"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/swarm/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/fortunto2/solo-factory/swarm"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/swarm.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.00053 | $0.01001 |
| Opus 5 | $0.00026 | $0.00500 |
| Sonnet 5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
solo-swarm 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/swarm
Create an agent team to research "$ARGUMENTS" from multiple perspectives in parallel.
Team Structure
Spawn 3 teammates, each with a distinct research focus:
1. Market Researcher
Focus: competitors, market size, pricing models, business models.
- Search for direct and indirect competitors
- Find market reports with TAM/SAM/SOM figures
- Analyze pricing strategies and monetization
- Identify market gaps and opportunities
- Check Product Hunt, G2, Capterra for existing products
2. User Researcher
Focus: pain points, user sentiment, feature requests.
- Search Reddit for user discussions (
site:reddit.com <query>via WebSearch, or MCPweb_searchif available) - Search Hacker News for tech community opinions (
site:news.ycombinator.com) - If MCP
session_searchavailable: check if this idea was researched before in past sessions - Find app reviews and ratings
- Extract direct user quotes about frustrations
- Identify unmet needs and feature requests
3. Technical Analyst
Focus: feasibility, tech stack, existing solutions, implementation complexity.
- Search GitHub for open-source alternatives (
site:github.com <query>) - Evaluate tech stack options
- If MCP
project_infoavailable: check existing projects for reusable code - If MCP
codegraph_explainavailable: get architecture overview of similar existing projects - If MCP
codegraph_queryavailable: find shared packages across projects - If MCP
project_code_searchavailable: search for reusable patterns, services, infrastructure across existing projects - Assess implementation complexity and timeline
Search Backends
Teammates should use available search tools:
- WebSearch (built-in) — broad discovery, market reports, always available
- WebFetch — scrape specific URLs for details, always available
- MCP
web_search(if available) — additional search with engine routing - MCP
web_extract(if available) — read a single page as clean markdown - MCP
kb_search(if available) — search local knowledge base for related research
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 · 88 lines · 53 tokens per session scan A a1244b7fe683
solo-swarm is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,001 once invoked, about $0.0003 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
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
dev-plan
Generate a development plan with task breakdown and section 10 tracking tables.
knowledge-feedback
Scan child projects for pitfalls and propose company standard updates.
sop-review
A structured code-review procedure for checking a task against project rules and acceptance criteria. It loads the task, relevant standards, and the Git changes before reviewing every required checkpoint.