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.
git 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/commands/fortunto2/solo-factory/investigate)<a href="https://agentmods.dev/commands/fortunto2/solo-factory/investigate"><img src="https://agentmods.dev/badge/commands/fortunto2/solo-factory/investigate/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/commands/fortunto2/solo-factory/investigate"><img src="https://agentmods.dev/badge/commands/fortunto2/solo-factory/investigate.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.00000 | $0.00230 |
| Opus 5 | $0.00000 | $0.00115 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
investigate 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.
What it actually says
/investigate — Debug Orchestrator
Command → Agent → Skill orchestration for investigating and fixing bugs.
Usage
/investigate <bug description or error message>
Orchestration Flow
Phase 1: Gather Evidence (Agent: code-analyst)
Spawn the code-analyst agent:
- Search codebase for related code paths
- Trace dependencies and call chains
- Identify likely root cause areas
Phase 2: Reproduce & Fix
Based on findings:
- Run the failing scenario as a background task to capture logs
- Read logs and error output
- Write a failing test that reproduces the bug
- Implement the fix
- Verify the test passes
Phase 3: Verify (Skill: /solo:review)
Quick review:
- Run full test suite
- Confirm no regressions
- Commit fix with descriptive message
Rules
- Always run log-producing processes as background tasks
- Write a regression test before fixing
- If root cause is unclear after Phase 1, ask the user — don't guess
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 · 34 lines · 0 tokens per session scan A c7c85a76b6f3
investigate is a command published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 230 tokens. 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 commands, from other repositories
harness-review
Review the current change set from an opposing harness-engineering perspective.
incident-patterns
Analyze recurring root causes and contributing factors across incidents. Provided by the Incident Review methodology.
unstuck
USE WHEN stuck on a bug, architecture decision, or recurring failure. Applies 5 perspectives sequentially (Researcher → Architect → Contrarian → Simplifier → Hacker) to break deadlock.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.