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 Vibe-Marketer/plugins-and-skills --skill ideal-customer-profilegit clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-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/vibe-marketer/plugins-and-skills/ideal-customer-profile)<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-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/vibe-marketer/plugins-and-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-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.00052 | $0.01361 |
| Opus 5 | $0.00026 | $0.00681 |
| Sonnet 5 | $0.00010 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
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 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<quick_start> Provide company/product information:
- What you sell and who it's for
- Industry/market focus
- Current customer examples (if available)
- Any existing marketing materials
I will generate a comprehensive ICP covering:
- Core demographics and organizational details
- Main challenges and desired outcomes
- Existing solutions and gaps
- Messaging triggers and conversion insights
- Buying process and timing signals </quick_start>
- What do you sell? (Product/service description)
- Who are your best customers? (Industry, company size, roles)
- What problem do you solve? (Pain points addressed)
- Any existing customer data? (Case studies, testimonials, patterns)
Review provided details and construct high-impact ICP based on core factors determining cold outreach success.
A. Core Demographics & Organizational Details
- Target Company Size: [Size]
- Geographic Location(s): [Location(s)]
- Industry/Sector: [Industry]
- Annual Revenue Range: [Range]
- Relevant Technologies: [Technologies they use]
- Team Structure: [Structure]
- Open Roles Signaling Need: [Hiring patterns indicating pain]
- External Signals: [Funding, growth, changes]
- Key Pain Points/Challenges: [Specific pains]
- Decision-Maker Roles: [Titles that buy]
B. Main Challenges & Goals
Top 1-2 Pain Points: [Biggest frustrations, urgent needs with specifics]
Desired Outcomes: [Key results they seek, KPIs that matter]
C. Existing Solutions & Gaps
Current Tools & Processes: [What they're already using]
Gaps & Shortcomings: [Where current solutions fall short]
D. Messaging Triggers & Conversion Insights
Must-Hit Topics: [Phrases or pain points that resonate most]
Likely Objections & Hesitations: [Price, complexity, trust issues]
Messaging Angles to Avoid: [Words/tones that push them away]
E. Message Testing Signals
Recent Campaign Language: [What competitors/industry leaders say that's working]
Community Sentiment: [Current hot topics/complaints in forums]
Terminology Shifts: [Industry jargon that's in vs. out]
F. Buying Process & Triggers
What Typically Triggers a Purchase? [Layoffs, funding, new leadership, pain threshold]
Decision-Making Timeline: [Immediate, 3-6 months, annual budgets] </step_1>
<step_2> Step 2: Extended ICP Details
Provide psychographic and behavioral insights to refine messaging.
Psychographics [Brand affinities, career motivations, communities]
Behavioral Insights
- Primary Research Channels: [Specific LinkedIn groups, subreddits, forums]
- Content Consumption: [Podcasts, newsletters, influencers they follow]
- Offline Presence: [Conferences, meetups, trade associations]
Cultural & Regional Nuances [Language, business norms]
Competitive Landscape [Key competitors, differentiation opportunities]
Success Stories & Proof Points [Case studies, testimonials, industry-specific results] </step_2>
<step_3> Step 3: Final Summary
Summarize ICP into concise, high-impact description (2-3 sentences) highlighting best messaging approach.
Connect ideal buyer's pain points, motivations, and conversion triggers. </step_3>
<output_format>
Ideal Customer Profile: [Company/Product]
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 · 233 lines · 52 tokens per session scan A c8e10c468220
ideal-customer-profile is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,361 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…