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 yuusakuri/agent-skills --skill ideal-customer-profilegit clone --depth 1 https://github.com/yuusakuri/agent-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/yuusakuri/agent-skills/ideal-customer-profile)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/ideal-customer-profile/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/yuusakuri/agent-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/ideal-customer-profile.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.00047 | $0.01231 |
| Opus 5 | $0.00023 | $0.00616 |
| Sonnet 5 | $0.00009 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
ideal-customer-profile 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.
This is a copy
100% identical to ideal-customer-profile — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideal Customer Profile
Overview
Identify your Ideal Customer Profile (ICP) from research and survey data. This skill synthesizes customer research to define the customer most likely to find value, retain, and expand with your product.
When to Use
- Defining ICP from product-market fit survey data
- Targeting high-value customer segments
- Analyzing customer success and expansion patterns
- Prioritizing sales and marketing efforts
- Evaluating new customer opportunities for fit
- Refining target market definition
ICP Framework Components
Demographics
Who are they from a firmographic and personal perspective?
- Company size (employees, revenue)
- Industry or vertical
- Geographic location
- Job title and department
- Years of experience in role
- Education and background
- Organizational structure and reporting
Behaviors
How do they work and make decisions?
- How they discover and evaluate solutions
- Buying process and decision-making timeline
- Technical literacy and product adoption speed
- Collaboration style (solo decision vs committee)
- Change management and adoption style
- Tool switching frequency
- Community involvement and peer influence
Jobs to Be Done (JTBD)
What are they trying to accomplish?
- Primary job/goal they're trying to achieve
- Secondary jobs that support the primary job
- Emotional jobs (how they want to feel)
- Social jobs (status and perception)
- Jobs they avoid or want to eliminate
- Frequency and importance of each job
- Success metrics for completing job
Needs and Pain Points
What problems does your product solve?
- Specific pain points they experience
- Current workarounds and limitations
- Impact on productivity or outcomes
- Cost or time burden of the problem
- Emotional frustration levels
- Barriers to solving the problem
- Available budget to solve
- Competing priorities
How It Works
Step 1: Gather Customer Data
Collect research about actual and potential customers:
- Product-market fit survey responses
- Customer interview transcripts
- Trial or freemium user behavior data
- Customer feedback and support tickets
- Churn analysis and customer lifecycle data
- Win/loss analysis from sales
- Competitor customer analysis
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 · 165 lines · 47 tokens per session scan A 8d434df786db
ideal-customer-profile is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,231 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ideal-customer-profile, differing in 0 lines, and is treated as a copy.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…