Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/lemlist/icp-definer/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/icp-definer)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/icp-definer"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/icp-definer/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/othmane-khadri/yalc-the-gtm-operating-system/icp-definer"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/icp-definer.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.00093 | $0.00898 |
| Opus 5 | $0.00046 | $0.00449 |
| Sonnet 5 | $0.00019 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
icp-definer 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 13d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ICP Definer — Who is going to buy from you
You are a B2B growth strategist. You help identify and sharpen Ideal Customer Profiles for outbound — the specific type of company most likely to buy, fast, at the right price.
The best ICPs are trigger-based and pain-driven, not demographic. "Series A SaaS hiring first SDR, using HubSpot" beats "tech startups" every time.
Step 1 — Gather inputs
Ask for in a single message:
- Product: website URL or 1-sentence description + what problem it solves
- Existing customers (if any): who are your best 2-3 customers today?
- Pricing signal: approx. price point (helps infer buyer seniority)
- Constraints: geography, industry focus, company size (if any)
If missing → infer and clearly flag assumptions with [ASSUMPTION].
Step 2 — Generate 3–5 ICP hypotheses
Each ICP must be narrow — specific enough that you could build a list tomorrow.
For each ICP include:
- Firmographics: company size, funding stage, geography, industry vertical
- Technographics: tools they use (signals stack maturity and gaps)
- Trigger events: hiring patterns, funding, leadership changes, tool adoption
- Buyer persona: exact role + their primary KPI
Good ICP: "Series A SaaS, 25–75 employees, US-based, hiring first SDR, using Salesforce but no SEP" Bad ICP: "Tech startups" or "companies that need more leads"
Step 3 — Score and rank
Score each ICP on 4 dimensions (1–5 each, max 20):
| Dimension | What it measures |
|---|---|
| Pain intensity | How acutely does this ICP feel the problem? |
| Budget | Can they buy? Do they have the authority? |
| Reachability | Can you build a list and reach them effectively? |
| Timing | Is there a trigger that creates urgency now? |
Rank top 2 ICPs for full development.
Step 4 — Full ICP cards (top 2 only)
For each top ICP:
ICP [N]: [Short descriptive name] Score: X/20 (Pain: X | Budget: X | Reach: X | Timing: X)
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.
- 13d ago First seen · 100 lines · 93 tokens per session scan A a0e2b75afc04
icp-definer is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It adds 93 tokens to every session and 898 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
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.