Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fortunto2/solo-factory/plugin install soloWrote 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/diagnose)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/diagnose"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/diagnose/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/diagnose"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/diagnose.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.00084 | $0.02121 |
| Opus 5 | $0.00042 | $0.01060 |
| Sonnet 5 | $0.00017 | $0.00424 |
| Haiku 4.5 | $0.00008 | $0.00212 |
Grade A, and why
solo-diagnose scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Phase 1 is done when you can name **one command** — a script path, a test invocation, a curl — that you have **already run at least once** (paste the invocation and its output), and that is: How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diagnose — the feedback loop is the skill
A discipline for hard bugs. Skip a phase only with an explicit reason.
Before exploring, read the project CLAUDE.md and any CONTEXT.md for the module vocabulary, and check ADRs in the area you're touching.
Phase 1 — Build a feedback loop
This is the skill. Everything else is mechanical. With a tight pass/fail signal that goes red on this bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume it. Without one, no amount of staring at code saves you.
Spend disproportionate effort here. Be aggressive, be creative, refuse to give up.
Ways to construct one — roughly in this order
- Failing test at whatever seam reaches the bug — unit, integration, e2e.
- Curl / HTTP script against a running dev server.
- CLI invocation with a fixture input, diffing stdout against a known-good snapshot.
- Headless browser script (Playwright MCP or a script) — drives the UI, asserts on DOM/console/network.
- Replay a captured trace. Save a real request / payload / event log to disk; replay it through the code path in isolation.
- Throwaway harness. A minimal subset of the system (one service, mocked deps) exercising the bug path in a single function call.
- Property / fuzz loop. For "sometimes wrong output": 1000 random inputs, look for the failure mode.
- Bisection harness. If it appeared between two known states (commit, dataset, version), automate "boot at state X, check, repeat" so
git bisect runcan eat it. - Differential loop. Same input through old vs new version (or two configs), diff the outputs.
- HITL bash script. Last resort — if a human must click, drive them with
scripts/hitl-loop.template.shso the loop stays structured and its output feeds back to you.
Servers and log streams run in the background (run_in_background: true) so the loop and the work proceed together.
Tighten the loop
Treat the loop as a product. Once you have a loop, tighten it:
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 · 141 lines · 84 tokens per session scan A 227211690eff
solo-diagnose is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 2,121 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-doctor
Run the diagnostic Harness Doctor workflow. Use when the user asks for /harness doctor, harness score, repository harness readiness, or a no-edit harness health report.
pitfall-record
Record a pitfall or lesson learned in the postmortem log.
pitfall-resolve
Mark a pitfall record as resolved in the postmortem log.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.