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 streamgit 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/stream)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/stream"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/stream.svg" alt="Measured on agentmods" 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.00055 | $0.01066 |
| Opus 5 | $0.00028 | $0.00533 |
| Sonnet 5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
solo-stream 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 8d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stream
Interactive wizard that walks any decision through the STREAM 6-layer framework. Designed for founders making high-stakes choices under uncertainty.
Steps
-
Parse the decision from
$ARGUMENTS. If empty, ask: "What decision or dilemma do you want to analyze?" -
Load framework context (optional enhancement):
- If MCP
kb_searchavailable:kb_search(query="STREAM framework", n_results=3)for full framework details. - Otherwise, the framework is embedded below.
- If MCP
-
Walk through 6 layers interactively. For each layer, explain the concept, ask a clarifying question via AskUserQuestion, then provide assessment.
Layer 1 — Epistemological (Knowledge)
- Is this within your circle of competence?
- What assumptions are unproven?
- What would change your mind?
- Ask: "What do you know for certain about this space? What are you assuming?"
Layer 2 — Temporal (Time)
- What's the time horizon for results?
- Is this Lindy-compliant (will it matter in 10 years)?
- Reversibility: can you undo this in 6 months?
- Ask: "What's your timeline? Is this a 3-month experiment or a 3-year commitment?"
Layer 3 — Action (Minimum Viable)
- What's the smallest possible first step?
- What are second-order effects?
- Can you test this in a weekend?
- Ask: "What's the minimum viable version you could ship in 1-2 weeks?"
Layer 4 — Stakes (Risk/Reward)
- Asymmetric upside? (small downside, large upside)
- Survivable worst case?
- Opportunity cost of NOT doing this?
- Ask: "What's the worst realistic outcome? Can you survive it financially and emotionally?"
Layer 5 — Social (Network)
- Reputation impact on your network?
- Network effects or viral potential?
- Does this build social capital?
- Ask: "Who benefits besides you? Who might be hurt?"
Layer 6 — Meta (Mortality Filter)
- Is this worth your finite time on earth?
- Does this align with your values?
- Will you regret NOT trying this?
- Ask: "If you had only 5 years left, would you still do this?"
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.
- 8d ago First seen · 116 lines · 55 tokens per session scan A 9a9363f9e5c4
solo-stream is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,066 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.
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.
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.