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 reviewgit 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/review)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/review"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/review/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/review"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/review.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.00046 | $0.07363 |
| Opus 5 | $0.00023 | $0.03682 |
| Sonnet 5 | $0.00009 | $0.01473 |
| Haiku 4.5 | $0.00005 | $0.00736 |
Grade A, and why
solo-review 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 — 721 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review
This skill is self-contained — follow the instructions below instead of delegating to external review skills (superpowers, etc.) or spawning Task subagents. Run all checks directly.
Final quality gate before shipping. Runs tests, checks security, verifies acceptance criteria from spec.md, audits code quality, and generates a ship-ready report with go/no-go verdict.
Live Context
- Branch: !
git branch --show-current 2>/dev/null - Diff stats: !
git diff --stat HEAD~3..HEAD 2>/dev/null | tail -5
When to use
After /deploy (or /build if deploying manually). This is the quality gate.
Pipeline: /deploy → /review
Can also be used standalone: /review on any project to audit code quality.
MCP Tools (use if available)
session_search(query)— find past review patterns and common issuesproject_code_search(query, project)— find similar code patterns across projectscodegraph_query(query)— check dependencies, imports, unused code
If MCP tools are not available, fall back to Glob + Grep + Read.
Pre-flight Checks
1. Architecture overview (if MCP available)
codegraph_explain(project="{project name}")
Returns: stack, languages, directory layers, key patterns, top dependencies, hub files. Use this to detect stack and understand project structure.
2. Essential docs (parallel reads)
CLAUDE.md— architecture, Do/Don't rulesdocs/plan/*/spec.md— acceptance criteria to verify (REQUIRED)docs/plan/*/plan.md— task completion status (REQUIRED)docs/workflow.md— TDD policy, quality standards, integration testing commands (if exists)
Do NOT read source code at this stage. Only docs.
3. Detect stack
Use stack from codegraph_explain response (or CLAUDE.md if no MCP) to choose tools:
- Next.js →
npm run build,npm test,npx next lint - Python →
uv run pytest,uv run ruff check - Swift →
swift test,swiftlint - Kotlin →
./gradlew test,./gradlew lint
4. Smart source code loading (for code quality spot check)
What ships with it
3 files 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 · 721 lines · 46 tokens per session scan A c03c0f1dd1af
solo-review is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 7,363 once invoked, about $0.0002 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
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
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.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.