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 jpeslar1/john-peslar-ai-skills --skill sales-pipeline-clinicgit clone --depth 1 https://github.com/jpeslar1/john-peslar-ai-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/jpeslar1/john-peslar-ai-skills/sales-pipeline-clinic)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-pipeline-clinic"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-pipeline-clinic/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/jpeslar1/john-peslar-ai-skills/sales-pipeline-clinic"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-pipeline-clinic.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.00056 | $0.00898 |
| Opus 5 | $0.00028 | $0.00449 |
| Sonnet 5 | $0.00011 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
sales-pipeline-clinic 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Pipeline Clinic
Work on the user's actual bottleneck. Produce one rewritten asset and one real test they can run this week. A more elegant email cannot fix an unfunded buyer or an undeliverable offer.
Build a minimal evidence pack
Use the seller's lane, buyer ICP/disqualifiers, offer, chosen channel, original asset, actual replies or call notes, recent stage counts, and current goal. Ask for the original text if it is missing; without it, produce a provisional draft and do not claim to have audited unseen copy.
Separate observed facts, interpretations, and missing data. Find the earliest failing stage: buyer fit, offer clarity, channel/list, message, meeting, or decision. Inspect contrary evidence before choosing a diagnosis. If counts use mixed periods or missing denominators, explain why the apparent leak is unproven.
Match the review to the asset
- ICP: pain, ability to fund, weekly reachability, and disqualifiers supported by real conversations.
- Offer: outcome, credible likelihood, time, buyer effort, clear stack, feasible risk reversal.
- Email/DM: one relevant idea, verified trigger, buyer language, cognitive load, ask appropriate to the relationship, and evidence behind every claim.
- Stuck deal: actual objection, decision criteria, approver path, owner, and mutually agreed next step.
For copy, count seller-centered versus buyer-centered language if it helps reveal the problem. I:you ratio is a diagnostic cue, not a rule to replace every "I" with "you" or claim better conversion. Remove premature pitching and unnecessary claims; preserve facts, intent, and the user's authorized offer.
Rewrite and test one thing
Provide the original asset, a concise diagnosis, and one recommended rewrite. Explain the few edits that change comprehension or the buyer's next decision. If the real failure is the ICP, change the ICP test rather than polishing irrelevant copy. Give additional variants only if requested or needed to test a meaningful alternative.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 54 lines · 56 tokens per session scan A 101540717514
sales-pipeline-clinic is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 898 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-09-09.
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…