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 customer-findergit 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/customer-finder)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/customer-finder"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/customer-finder/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/customer-finder"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/customer-finder.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.00077 | $0.01842 |
| Opus 5 | $0.00039 | $0.00921 |
| Sonnet 5 | $0.00015 | $0.00368 |
| Haiku 4.5 | $0.00008 | $0.00184 |
Grade A, and why
solo-customer-finder 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 11d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/customer-finder
Turn a product URL or idea into a short, evidence-backed list of plausible FIRST customers. Every prospect must link to a public pain/demand/timing signal — a company that merely matches the industry is NOT a prospect. Output is a research hypothesis, not a customer database.
Difference from /community-outreach: that skill finds threads to reply in; this one finds named prospects (companies, projects, public professionals) with scores and outreach openers.
MCP Tools (use if available)
web_search(query, engines, include_raw_content)— SearXNG with engine routing (Reddit, HN, GitHub)web_extract(url, size, page)— one page as clean markdown, paginated for long docskb_search(query)— prior research in KBproject_info(name)— project details
Fallback: WebSearch/WebFetch.
Steps
-
Product brief. Parse
$ARGUMENTS(project slug, URL, or idea + optional mode). Readdocs/prd.mdanddocs/research.mdif present — reuse ICP, pain points, competitors instead of re-deriving. Define: product + promised outcome, primary user vs economic buyer, urgent job-to-be-done, current workaround, adoption trigger, geography/language, disqualifiers. One primary ICP + one adjacent. Don't start searching until the brief is specific enough to REJECT weak matches. Ask one question via AskUserQuestion only if ambiguity would change the search. -
Query buckets. Search several angles, not one query repeated (adapt wording to the audience's language):
- Explicit demand: "looking for", "recommend a tool", "alternative to", "does anything exist"
- Pain: "takes hours", "manual", "frustrating", "keeps breaking"
- Workaround: spreadsheets, copy-paste, scripts, VAs, repeated manual steps
- Switching: cancellation, migration, missing feature, pricing complaints
- Timing: launch, hiring, expansion, new regulation/integration relevant to the product
-
Search public sources (parallel): forums/Reddit, HN, product & marketplace reviews, GitHub issues and feature requests, public company pages / job posts / changelogs, "looking for a tool" posts. Open the original page — never qualify from a search snippet. Record: source URL, type, visible date (or "date unavailable"), exact evidence quote (minimal) or paraphrase.
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.
- 11d ago First seen · 131 lines · 77 tokens per session scan A 05a9a78aebf9
solo-customer-finder is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,842 once invoked, about $0.0004 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.
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.
dev-plan
Generate a development plan with task breakdown and section 10 tracking tables.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-update
Refresh an adopted target repository from the latest Harness Starter Kit reference. Use when the user asks for /harness update or wants source tracking and selective harness updates.