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 cmj-hub/claude-evp --skill evp-onboardinggit clone --depth 1 https://github.com/cmj-hub/claude-evpWrote 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/cmj-hub/claude-evp/evp-onboarding)<a href="https://agentmods.dev/skills/cmj-hub/claude-evp/evp-onboarding"><img src="https://agentmods.dev/badge/skills/cmj-hub/claude-evp/evp-onboarding/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/cmj-hub/claude-evp/evp-onboarding"><img src="https://agentmods.dev/badge/skills/cmj-hub/claude-evp/evp-onboarding.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.00091 | $0.01205 |
| Opus 5 | $0.00046 | $0.00602 |
| Sonnet 5 | $0.00018 | $0.00241 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
evp-onboarding 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 yesterday.
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
86% identical to os-self-test — 181 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EVP Onboarding — first-run setup
10 minutes of setup that makes every downstream EVP differentiated instead of generic.
Activation
Loaded automatically by evp orchestrator when brand-config.json
or SOUL.md is missing.
Also user-invocable: "Set up EVP brand config", "EVP onboarding".
Workflow
Step 1 — ICP + PSP carry-forward
Quick check — do you already have a PSP?
If yes (claude-psp is installed and PSP doc exists): I'll pull ICP + pain + vocabulary from there.
If no: Install cmj-hub/claude-psp first. EVP without a PSP is a guess.
Step 2 — Primary outreach tier
Where is YOUR buyer on the Schwartz tier ladder when they meet you?
Most B2B buyers live in Tiers 2-4. Pick the most common one for your outreach:
Tier 1 (unaware) — you have to reveal the pain first
Tier 2 (problem-aware) — they know the pain, no solutions evaluated
Tier 3 (solution-aware) — they're comparing categories (in-house / agency / tool)
Tier 4 (product-aware) — comparing specific vendors
Tier 5 (most aware) — ready to buy
If you don't know, default to Tier 3 — most outbound campaigns target
that tier.
Save to brand-config.primary_outreach_tier.
Step 3 — Outcomes-I-will-claim list
What specific outcomes are you willing to claim in writing?
Each outcome needs:
1. A specific noun (not a verb — "14 SQLs", not "more pipeline")
2. A specific timeframe (in 30 days, per month, per quarter)
3. A proof point you can back it with
Examples of GOOD outcomes:
"14+ SQLs per month"
"Targeted-outbound CPM under $700"
"First positive reply within 7 days"
Examples of BAD outcomes (refuse to claim):
"Better demand-gen"
"Improved efficiency"
"Best-in-class outreach"
Give me 3-5 outcomes you're willing to claim. These constrain every
downstream EVP variant.
Save to SOUL.md (outcomes-I-will-claim list) + brand-config.evp_drafts.tier_3.outcome.
Step 4 — Tradeoffs you name
For each outcome, what's the obvious tradeoff you spare them from?
The EVP shape is "<outcome> without <tradeoff>". The tradeoff carries
the line — name something they'd otherwise have to give up.
Examples:
"without hiring 2 more SDRs"
"without breaking the PLG self-serve motion"
"without paying agency retainer rates"
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.
- yesterday Changed 2ef42bd22b15
- 9d ago First seen · 164 lines · 91 tokens per session scan A 694df83027e5
evp-onboarding is a skill published in the GitHub repository cmj-hub/claude-evp (2 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,205 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to os-self-test, differing in 181 lines, and is treated as a copy.
Other skills, from other repositories
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
psp
Pain Signal Profile (PSP) builder for B2B operators. Translates public, recent, verifiable signals (job posts, funding rounds, leadership changes, product launches, pricing changes, hiring patterns) into the felt operational pain that drives buying decisions — and then into the EVP that speaks to it. Anchors every…
psp-onboarding
First-run interactive setup for the PSP skill pack. Walks the operator through brand-config.json (ICP precision, exclusion criteria, signal sources) and SOUL.md (buyer vocabulary, stories, the 11am-Tuesday moment) in 15 minutes. Refuses to let the operator skip — generic PSP output is worse than no PSP. Loaded…
psp-construct
Step-by-step construction of a Pain Signal Profile for a specific ICP segment. Walks operator through the 5 components (signal, pain, timing, role, vocabulary), validates each, and produces a structured PSP doc. Loaded by the main psp skill when the user wants to build a PSP from scratch.
psp-kickoff
Adaptive router for the PSP skill pack. Detects state (brand-config? SOUL.md? primary PSP drafted? secondary PSPs? vocabulary refreshed?) and picks the next-best step. Loaded by the main psp skill on bare invocation. Inspired by the coldoutboundskills kickoff pattern.
psp-signal-hunt
Surface 5-10 public, recent, verifiable signals worth hunting for a given ICP segment. Catalogs signal types (hiring, funding, leadership, product, pivot, content) and proposes operational sources + cadence to track each. Loaded by the main psp skill when the user wants to find what signals to hunt.