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 scaffoldgit 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/scaffold)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/scaffold"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/scaffold/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/scaffold"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/scaffold.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.00058 | $0.03123 |
| Opus 5 | $0.00029 | $0.01562 |
| Sonnet 5 | $0.00012 | $0.00625 |
| Haiku 4.5 | $0.00006 | $0.00312 |
Grade A, and why
solo-scaffold 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scaffold
Scaffold a complete project from PRD + stack template. Creates directory structure, configs, CLAUDE.md, git repo, and pushes to GitHub. Studies existing projects via SoloGraph for consistent patterns, uses Context7 for latest library versions.
Steps
-
Parse arguments from
$ARGUMENTS— extract<project-name>and<stack-name>.- If not provided or incomplete, use AskUserQuestion to ask for missing values.
- Show available stacks from
templates/stacks/*.yaml(source of truth). If MCPproject_infoavailable, also show detected stacks from active projects. List stack names with one-line descriptions from each YAML'sdescriptionfield. - Project name should be kebab-case.
-
Load org defaults from
~/.solo-factory/defaults.yaml:- Read
org_domain(e.g.com.mycompany),apple_dev_team,github_org,projects_dir - If file doesn't exist, ask via AskUserQuestion:
- "What is your reverse-domain prefix for bundle IDs?" (e.g.
com.mycompany) - "Apple Developer Team ID?" (optional, leave empty if no iOS)
- "What is your reverse-domain prefix for bundle IDs?" (e.g.
- Create
~/.solo-factory/defaults.yamlwith answers for future runs - Replace
<org_domain>,<apple_dev_team>,<github_org>placeholders in all generated files
- Read
-
Load stack + PRD + principles:
- Look for stack YAML: search for
stacks/<stack>.yamlin plugin templates (viakb_searchor Glob). - If stack YAML not found, use built-in knowledge of the stack (packages, structure, deploy).
- Check if PRD exists:
docs/prd.mdor search current directory forprd.md- If not: generate a basic PRD template
- Look for dev principles: search for
dev-principles.mdanddev-principles-my.md(personal extensions) or use built-in SOLID/DRY/KISS/TDD principles.
- Look for stack YAML: search for
-
Study existing projects via SoloGraph (learn from your own codebase — critically):
Before generating code, study active projects with the same stack. Don't blindly copy — existing projects may have legacy patterns or mistakes. Evaluate what's actually useful.
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.
- 10d ago First seen · 240 lines · 58 tokens per session scan A 0ca4d1be0665
solo-scaffold is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 3,123 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.
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.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-review
Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.