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 content-gengit 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/content-gen)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/content-gen"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/content-gen/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/content-gen"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/content-gen.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.00057 | $0.01606 |
| Opus 5 | $0.00028 | $0.00803 |
| Sonnet 5 | $0.00011 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
solo-content-gen 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/content-gen
Generate a promotion content pack from a project's PRD or README. Produces 3 ready-to-use content pieces: LinkedIn post, Reddit answer draft, and Twitter/X thread. For video scripts, use /video-promo.
MCP Tools (use if available)
kb_search(query)— find related methodology and principlesproject_info(name)— get project details, stack, descriptionproject_code_search(query, project)— find key features in codebase
If MCP tools are not available, fall back to Glob + Grep + Read.
Steps
-
Parse project from
$ARGUMENTS.- If project name: find PRD at
docs/prd.md, or README.md, or CLAUDE.md. - If path: read directly.
- If empty: ask via AskUserQuestion — "Which project to generate content for?"
- If project name: find PRD at
-
Extract core messaging from PRD/README (parallel reads):
- Problem: What pain does this solve? (1 sentence)
- Solution: What does the product do? (1 sentence)
- ICP: Who is the target user? (persona)
- Key features: Top 3-5 differentiating features
- Unique angle: What nobody else does (gap from research.md if exists)
- Social proof: Any metrics, users, downloads (if available)
-
Forced reasoning — messaging framework: Before generating content, write out:
- Hook: What stops the scroll? (pain point or surprising stat)
- Proof: Why should they believe you? (demo, numbers, authority)
- CTA: What's the one action? (try, sign up, download)
- Tone: Based on ICP — casual/professional/technical/friendly
-
Generate content pieces:
4a. LinkedIn Post
Format: Hook line → Story (before/after) → Insight → CTA
- 1300-1500 chars max
- First line is the hook (visible before "see more")
- Use line breaks for readability
- End with question to drive engagement
4b. Reddit Answer Draft
Format: Helpful answer that naturally mentions the product
- NOT promotional — value-first, product mention is secondary
- Suggest 3-5 subreddits where this would be relevant
- Write as if answering someone's genuine question
- Include "disclaimer: I built this" transparency
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 · 165 lines · 57 tokens per session scan A b99e20178843
solo-content-gen is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,606 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.