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 travisjneuman/.claude --skill customer-persona-buildergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/customer-persona-builder)<a href="https://agentmods.dev/skills/travisjneuman/.claude/customer-persona-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/customer-persona-builder/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/travisjneuman/.claude/customer-persona-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/customer-persona-builder.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.00040 | $0.02907 |
| Opus 5 | $0.00020 | $0.01453 |
| Sonnet 5 | $0.00008 | $0.00581 |
| Haiku 4.5 | $0.00004 | $0.00291 |
Grade A, and why
customer-persona-builder 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.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Persona Builder
Structured frameworks for creating data-driven customer personas, ideal customer profiles, and user archetypes.
Persona vs ICP Distinction
When to Use Which
IDEAL CUSTOMER PROFILE (ICP):
- Company-level / account-level description
- Used by: Sales, marketing (targeting), product (roadmap)
- Answers: "What companies should we sell to?"
- Firmographic: industry, size, revenue, tech stack
BUYER PERSONA:
- Individual-level description
- Used by: Sales (conversations), marketing (messaging), content
- Answers: "Who are the people making buying decisions?"
- Behavioral: goals, pain points, decision process
USER PERSONA:
- End-user description (may differ from buyer)
- Used by: Product, design, engineering
- Answers: "Who uses the product daily?"
- Task-based: workflows, jobs-to-be-done, frustrations
RELATIONSHIP:
ICP (company) contains multiple Buyer Personas (people)
who may differ from User Personas (daily users).
Ideal Customer Profile Template
ICP Framework
IDEAL CUSTOMER PROFILE:
FIRMOGRAPHICS:
- Industry: [specific verticals]
- Company Size: [employee range]
- Annual Revenue: [revenue range]
- Geography: [regions/countries]
- Growth Stage: [startup/growth/enterprise]
TECHNOGRAPHICS:
- Current Stack: [tools they use today]
- Infrastructure: [cloud, on-prem, hybrid]
- Maturity: [early adopter, mainstream, laggard]
BUSINESS CHARACTERISTICS:
- Pain Intensity: [how acute is the problem we solve]
- Budget Authority:[does this level have budget]
- Buying Process: [simple, committee, procurement]
- Contract Value: [expected ACV range]
QUALIFYING SIGNALS:
- Positive: [hiring for X role, using Y tool, in Z market]
- Negative: [too small, wrong industry, already solved]
DISQUALIFYING CRITERIA:
- [specific reasons to exclude]
ICP Scoring Matrix
| Attribute | Ideal (5) | Good (3) | Poor (1) | Weight |
|---|---|---|---|---|
| Industry | [exact verticals] | [adjacent verticals] | [unrelated] | 20% |
| Company Size | [sweet spot range] | [workable range] | [too small/large] | 15% |
| Pain Intensity | Active seeking solution | Aware of problem | Unaware | 25% |
| Budget | Dedicated budget exists | Can find budget | No budget | 20% |
| Tech Fit | Perfect stack match | Partial overlap | Incompatible | 10% |
| Champion | Identified internal advocate | Potential champion | No access | 10% |
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.
- 9d ago First seen · 376 lines · 40 tokens per session scan A b6628b71b392
customer-persona-builder is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 2,907 once invoked, about $0.0002 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.
Other skills, from other repositories
plan-review-architecture
Architecture-dimension reviewer for written plans. Use when running plan-review or directly when an architectural review is wanted. Activate for keywords like "architecture review", "data flow", "failure modes", "rollback", "edge cases", "test matrix". Scores 5 sub-dimensions 0-10, produces ranked fixes. Always cite…
plan-review-experience
Experience-dimension reviewer for written plans (UX + DX). Use when running plan-review or directly when an experience review is wanted. Activate for keywords like "UX review", "DX review", "experience review", "error states", "API ergonomics", "developer experience", "user states". Scores 5 sub-dimensions 0-10…
audit-dependencies
Use when investigating dependency bloat, security advisories, supply-chain risk, upgrade planning, or before adding a new third-party package. Activate for keywords like "deps", "dependencies", "package.json", "requirements.txt", "Cargo.toml", "audit", "CVE", "stale package", "do we use", "what depends on"…
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…