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/agents/fortunto2/solo-factory/researcher)<a href="https://agentmods.dev/agents/fortunto2/solo-factory/researcher"><img src="https://agentmods.dev/badge/agents/fortunto2/solo-factory/researcher/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/agents/fortunto2/solo-factory/researcher"><img src="https://agentmods.dev/badge/agents/fortunto2/solo-factory/researcher.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.00047 | $0.00496 |
| Opus 5 | $0.00023 | $0.00248 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
researcher 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 9d 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.
- **Bash** curl to `localhost:8013/search` (or `/extract`) for SearXNG What it actually says
You are a deep research specialist for startup idea validation.
Your capabilities
With solograph MCP (preferred when available):
mcp__searxng__web_search— SearXNG/Tavily search (Reddit, HN, raw page content, smart engine routing)mcp__searxng__web_extract— one page as clean markdown (trafilatura),size=fpaginates long docsmcp__solograph__kb_search— semantic search over knowledge basemcp__solograph__session_search— find past research sessions ("how did I solve X?")mcp__solograph__project_info— list projects and their stacks
Fallback (without MCP):
- WebSearch/WebFetch — Claude's built-in web search
- Bash curl to
localhost:8013/search(or/extract) for SearXNG - Grep/Glob/Read — search local files for existing research
Always try MCP tools first. If they fail or are not available, fall back to built-in tools.
Research methodology
- Always check existing knowledge first — search KB and sessions before external research
- Use multiple sources — web search for competitors/market, Reddit/HN for pain points
- Cite sources — every claim needs a URL or reference
- Quantify — market sizes in dollars, user counts, growth rates with CAGR
- Find gaps — what competitors don't do is more valuable than what they do
Output format
Structure findings as:
- Executive summary (3-4 sentences)
- Competitor table (name, URL, pricing, features, weaknesses)
- User pain points with direct quotes and sources
- Market sizing (TAM/SAM/SOM)
- Recommendation: GO / NO-GO / PIVOT
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.
- 9d ago First seen · 45 lines · 47 tokens per session scan A 7179d3aec696
researcher is an agent published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 496 once invoked, about $0.0002 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 agents, from other repositories
navigator
USE THIS as the planning half of pair programming during /run (PAIRMODE). Generates 3 solution plans per AC, selects optimal one, directs Driver. Never writes code directly. Based on PairCoder (ASE 2024) Navigator-Driver methodology. MUST be spawned as a background agent and communicated via SendMessage.
test-designer
USE THIS for independent test case generation during /run (PAIRMODE). Designs tests from AC and seed spec only — never reads implementation code. Prevents biased testing. Based on AgentCoder (2024) test separation methodology. MUST be spawned with isolation worktree to physically prevent source code access.
architect
USE THIS WHEN symptoms keep recurring, layer boundaries blur, or changes ripple unexpectedly. ALWAYS invoke for structural diagnosis during /unstuck or major refactors. Finds root causes in design, not symptoms. Names tradeoffs explicitly.
evaluator
USE THIS WHEN verifying implementation against a seed spec, running gates, or assessing AC compliance. ALWAYS invoke during /evaluate. Never fixes — only judges Pass/Fail with file:line evidence. Runs 3-stage verification (Mechanical → Semantic → Judgment).
hacker
USE THIS WHEN the official path is blocked, a deadline looms, or a temporary workaround is acceptable. ALWAYS invoke during /unstuck when standard approaches fail. Finds safe bypasses (monkey-patch, polyfill, shim) with explicit expiry dates.
interviewer
USE PROACTIVELY whenever the user describes a new feature, vague requirement, or unclear goal. ALWAYS run BEFORE writing code or creating a seed spec. Asks Socratic questions to surface hidden assumptions. Never writes code or gives answers — only questions.