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 mardab96/b2b-lead-generation-claude-skills --skill icp-reality-checkgit clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-skillsWrote 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/mardab96/b2b-lead-generation-claude-skills/icp-reality-check)<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/icp-reality-check"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/icp-reality-check/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/mardab96/b2b-lead-generation-claude-skills/icp-reality-check"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/icp-reality-check.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.00050 | $0.00962 |
| Opus 5 | $0.00025 | $0.00481 |
| Sonnet 5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
icp-reality-check 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Icp Reality Check
Use the shared quality bar in ../references/output-standard.md and ../references/skill-design-principles.md when those files are available.
Use this skill when
- the user shares lead source, CRM stage, sales note, form, landing page or campaign data tied to icp reality check.
- the next decision could change targeting, qualification, scoring, follow-up, sales handoff or budget.
- lead volume looks acceptable but SQL, opportunity, closed-won, rejection or response-speed data raises doubt.
Do not use this skill for broad lead-generation advice without source, CRM, sales or qualification evidence. Use it when a real B2B lead quality decision is on the table.
Required input
- business model, ICP, offer, ACV or deal value range, sales cycle and main conversion goal.
- ad, landing page, lead form, CRM, call note, email or campaign data relevant to this diagnostic.
- time window, traffic source, lead volume and downstream outcomes where available.
- what decision the user is trying to make next: create, fix, scale, pause, brief sales or investigate.
- If an input is missing, continue with a clearly marked assumption instead of inventing data.
Analysis workflow
- Write the stated ICP as a short profile: company type, buyer role, pain, budget, urgency and exclusion rules.
- Build a comparison table for closed-won, closed-lost, disqualified and no-show leads by source, company size, role, industry, use case and deal value.
- Identify ICP drift: segments that produce cheap leads but weak SQL/opportunity/closed-won rates.
- Find ICP blind spots: segments with low lead volume but high sales acceptance or deal value.
- Separate targeting problems from offer, page, qualification and follow-up problems before recommending a change.
- Return an ICP action: keep, narrow, split into segments, exclude, or collect more data.
Diagnostic rubric
Use this table when the user provides CRM or sales outcome data:
| Segment | Lead volume | SQL rate | Opportunity rate | Closed-won rate | Rejection pattern | ICP verdict |
|---|---|---|---|---|---|---|
| Company size / role / industry / use case | Count and source mix | Percent or missing-data marker | Percent or missing-data marker | Percent or missing-data marker | Sales reason, no-show pattern or lost reason | Keep / narrow / split / exclude / collect more data |
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.
- 12d ago First seen · 80 lines · 50 tokens per session scan A 80b0c15cf238
icp-reality-check is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 962 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…