icp-deep-scanner

icp-deep-scanner is a skill for Claude Code, Codex from OneWave-AI/claude-skills. It costs 90 tokens per session (1,632 once invoked), scanned A, original, MIT.

A read-only workflow that examines connected business data to build an Ideal Customer Profile, meaning a description of the customers most likely to benefit from a product, plus reusable buyer personas.

In plain words
What is it for?
Use it to analyse best customers, won and lost deals, support tickets, reviews, and other connected data for marketing and product decisions.
Why use it?
It bases customer definitions on actual sales, support, review, and billing evidence rather than assumptions made in a presentation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: model in frontmatter; mentions subagents.

Good fit Use it to analyse best customers, won and lost deals, support tickets, reviews, and other connected data for marketing and product decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/onewave-ai/claude-skills/icp-deep-scanner
Install

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.

Any agent
npx skills add OneWave-AI/claude-skills --skill icp-deep-scanner
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/claude-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for icp-deep-scanner

README.md
[![agentmods](https://agentmods.dev/badge/skills/onewave-ai/claude-skills/icp-deep-scanner/github.svg)](https://agentmods.dev/skills/onewave-ai/claude-skills/icp-deep-scanner)
Your own site
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/icp-deep-scanner"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/icp-deep-scanner/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.

agentmods 80×15 button for icp-deep-scanner

Your own site · 80×15
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/icp-deep-scanner"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/icp-deep-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,632 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.01632
Opus 5 $0.00045 $0.00816
Sonnet 5 $0.00018 $0.00326
Haiku 4.5 $0.00009 $0.00163

Measured 9d ago against content hash 7f320652dfc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

icp-deep-scanner 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 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.

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.

icp-deep-scanner/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ICP Deep Scanner

Turn the data already sitting in your connected tools into a rigorous, evidence-backed Ideal Customer Profile (ICP) and a library of buyer personas. Most ICPs are invented in a slide deck. This one is reverse-engineered from your actual best customers, your won/lost deals, your support tickets, and your reviews — then written so it can drive real decisions and feed the panel skills.

This skill is the data layer beneath customer-panel-of-experts, prospect-panel-simulator, and product-launch-war-room. Run it first; those skills read the persona library it writes.

Operating principles (read first)

  • Read-only by default. You may query and read connected sources. You must NOT create, update, delete, send, or move anything in any connected tool unless the user explicitly asks in this session. Before any write or outbound action, stop and confirm.
  • Least data necessary. Pull aggregates and representative samples, not entire databases. You are building a profile, not exfiltrating a CRM.
  • PII minimization. Persona artifacts are archetypes, not dossiers. Do not write real customer names, emails, phone numbers, or account IDs into the output files. Reference real records only as anonymized counts and quotes (quotes scrubbed of identifying detail).
  • Secrets via environment only. Never read, print, or write credentials. Assume tokens live in environment variables (e.g. $SUPABASE_TOKEN, $OPENAI_API_KEY) or in the MCP connection itself. If a source needs auth that isn't present, list it under "Sources I could not reach" and continue.
  • Cite the evidence. Every claim in the ICP must trace to a source. "Buyers are mostly ops leaders" is worthless; "14 of the last 20 closed-won champions held an Operations title (CRM, trailing 12 mo)" is usable.

Step 1 — Inventory connectable sources

Ask the user which tools to scan, or detect what's available. Map each to what it tells you:

Source (examples) What to extract How to reach it
CRM (HubSpot, Salesforce, internal) Closed-won vs closed-lost firmographics, titles of champions/buyers, deal size, sales cycle, win reasons MCP connector or read-only API
Email / calendar Who actually engages, meeting cadence, recurring objection language Gmail/Calendar MCP, read-only
Support / tickets / chat Top pain themes, words customers use, where they get stuck Intercom/Zendesk export, logs
Reviews (G2, Capterra, Trustpilot, App Store) Verbatim value language, switching triggers, deal-breakers WebFetch / customer-review-aggregator
Product analytics (GA4, Clarity, Mixpanel) Activation paths, who sticks, drop-off points Analytics MCP / API
Billing (Stripe, Mercury) Real revenue concentration, expansion vs churn by segment Read-only API
Database (Supabase/Postgres) Ground-truth usage and cohort behavior Read-only SQL via $SUPABASE_TOKEN
Public web Firmographic enrichment, market sizing, competitor positioning WebSearch / WebFetch

Read the full file on GitHub · 113 lines

Changes

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.

  1. 9d ago First seen · 113 lines · 90 tokens per session scan A 7f320652dfc6

Subscribe to this mod's changes

icp-deep-scanner is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,632 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-09-03.

Related

Other skills, from other repositories

analytics-strategy

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…

rampstackco/claude-skills · 126 tokens

content-strategy

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…

rampstackco/claude-skills · 120 tokens

incident-response

Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…

rampstackco/claude-skills · 117 tokens

stakeholder-communication

Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…

rampstackco/claude-skills · 103 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

agb-begriff-vorformuliert-305

Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.

Klotzkette/claude-fuer-deutsches-recht · 68 tokens