Codex First Customer Finder Skill is a Codex skill that researches public signals to identify likely early customers for a startup or product. It defines customer profiles, evaluates prospect fit and timing, cites supporting sources, and produces a report with manual outreach suggestions. Its catalogue add-ons provide the skill’s workflow for coding agents.
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 Kappaemme-git/codex-first-customer-finder-skill --skill first-customer-findergit clone --depth 1 https://github.com/Kappaemme-git/codex-first-customer-finder-skillWrote 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/kappaemme-git/codex-first-customer-finder-skill/first-customer-finder)<a href="https://agentmods.dev/skills/kappaemme-git/codex-first-customer-finder-skill/first-customer-finder"><img src="https://agentmods.dev/badge/skills/kappaemme-git/codex-first-customer-finder-skill/first-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/kappaemme-git/codex-first-customer-finder-skill/first-customer-finder"><img src="https://agentmods.dev/badge/skills/kappaemme-git/codex-first-customer-finder-skill/first-customer-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.01116 |
| Opus 5 | $0.00048 | $0.00558 |
| Sonnet 5 | $0.00019 | $0.00223 |
| Haiku 4.5 | $0.00010 | $0.00112 |
Grade A, and why
first-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- customer-finder — 97% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Customer Finder
Turn a startup URL or product description into a short, evidence-backed list of plausible first customers. Use public signals, preserve privacy, and distinguish a prospect from a confirmed buyer.
Read references/research-framework.md before researching or scoring prospects. Read references/report-artifact.md before creating the final report.
Workflow
1. Understand the product
- Inspect the supplied URL, repository, landing-page copy, or product description.
- Identify the product, outcome, buyer, user, price or buying motion, geography, and strongest use case.
- Define one primary ICP, one adjacent ICP, pain triggers, positive signals, and disqualifiers.
- Infer missing context when safe and label the inference. Ask one concise question only when ambiguity would materially change the search.
2. Build a public-signal search plan
Search current public sources for:
- explicit tool or alternative requests
- first-person descriptions of the target problem
- manual workflows and repeated workaround complaints
- migration, churn, or competitor-frustration signals
- public company changes that create timing, such as hiring, launching, expanding, or adopting a relevant workflow
Use multiple query angles and source types. Prefer original pages over search snippets. Record the source URL, source type, publication date when visible, and the exact evidence supporting qualification.
3. Research safely
- Use public, intentionally shared professional or business information only.
- Do not bypass login walls, paywalls, access controls, rate limits, or robots restrictions.
- Do not use data brokers, leaked datasets, private groups, personal email discovery, phone enrichment, or sensitive personal information.
- Do not infer protected traits or target people using health, financial hardship, political belief, sexuality, religion, or other sensitive attributes.
- Prefer companies, public professional profiles, public requests, and community posts relevant to the product.
- Quote minimally and paraphrase by default. Link every material pain or timing signal.
What ships with it
4 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 · 102 lines · 95 tokens per session scan A ae8a2fcd1368
first-customer-finder is a skill published in the GitHub repository Kappaemme-git/codex-first-customer-finder-skill (1,035 stars, last pushed 17d ago), licensed MIT. It adds 95 tokens to every session and 1,116 once invoked, about $0.0005 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
gingiris-user-interview
A playbook for interviewing users and operating an early product launch, including screening participants, running interviews, testing beta versions, and reviewing churn. It is based on a described process for finding product-market fit, meaning a product consistently meeting a real user need.
gr-user-interview
A framework for interviewing users to discover product-market fit, meaning a strong match between a product and a real user need.
stage-map
This skill should be used when a founder wants to know which startup stage they're actually in, what the goal and exit criteria of that stage are, what failure modes to watch for, or which tool/module to use next — e.g. "what stage am I at", "what should I focus on now", "am I ready for an MVP", "do I have…
first-customer-finder
Find and qualify evidence-backed potential first customers, early adopters, design partners, or beta users for a startup from recent public signals. Trigger on "find my first customers", "who would buy this", "find early adopters", "find design partners", "find beta users", "find leads for my startup", or when given a…
idea-stage
This skill should be used when a founder wants to validate, pressure-test, or kill a startup/product idea before building it — sharpening a hunch into a testable hypothesis, red-teaming it, sizing the market, mapping competitors, designing and synthesizing customer-discovery interviews, and deciding whether the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…