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 pipelinegit 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/pipeline)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/pipeline"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/pipeline/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/pipeline"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/pipeline.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.00061 | $0.01226 |
| Opus 5 | $0.00030 | $0.00613 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
solo-pipeline 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pipeline
Launch an automated multi-skill pipeline. The Stop hook chains skills automatically — no manual invocation needed between stages.
Available Pipelines
Research Pipeline
/pipeline research "AI therapist app"
Chains: /research -> /validate
Produces: research.md -> prd.md
Dev Pipeline
/pipeline dev "project-name" "stack"
/pipeline dev "project-name" "stack" --feature "user onboarding"
Chains: /scaffold -> /setup -> /plan -> /build
Produces: full project with workflow, plan, and implementation
Steps
1. Parse Arguments
Extract from $ARGUMENTS:
- Pipeline type: first word (
researchordev) - Remaining args: passed to the launcher script
If no arguments or unclear, ask:
Which pipeline do you want to run?
1. Research Pipeline — /research → /validate (idea to PRD)
2. Dev Pipeline — /scaffold → /setup → /plan → /build (PRD to running code)
2. Confirm with User
Show what will happen:
Pipeline: {type}
Stages: {stage1} → {stage2} → ...
Idea/Project: {name}
This will run multiple skills automatically. Continue?
Ask via AskUserQuestion.
3. Start First Stage
Run the first skill in the pipeline directly:
For research pipeline: Run /research "idea name"
For dev pipeline: Run /scaffold project-name stack
The Stop hook (if configured) will handle subsequent stages automatically. Without a Stop hook, manually invoke each skill in sequence.
3b. Launcher Scripts (optional, Claude Code plugin only)
If you have the solo-factory plugin installed, launcher scripts provide tmux dashboard and logging:
# Only available with Claude Code plugin — skip if not installed
solo-research.sh "idea name" [--project name]
solo-dev.sh "project-name" "stack" [--feature "desc"]
Pass --no-dashboard when running from within a skill context.
5. Pipeline Completion
When all stages are done, output:
<solo:done/>
The Stop hook checks for this signal and cleans up the state file.
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 · 162 lines · 61 tokens per session scan A d31d3bf2ce9e
solo-pipeline is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,226 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.