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-discovery-call-coachgit 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-discovery-call-coach)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-discovery-call-coach"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-discovery-call-coach/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-discovery-call-coach"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-discovery-call-coach.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.00894 |
| Opus 5 | $0.00026 | $0.00447 |
| Sonnet 5 | $0.00010 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
sales-discovery-call-coach 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Discovery Call Coach
Prepare a conversation that establishes whether working together makes sense. When reviewing a call, use the actual notes or transcript; do not infer commitments from positive tone.
Before the call
Use the buyer's role, verified trigger, ICP, offer, known workflow, available meeting time, and existing correspondence. Separate known facts, hypotheses, and questions. If context is thin, produce a general agenda and flag the claims that cannot yet be personalized.
Draft an opening under 60 seconds: agree the purpose, available time, permission to ask about the current process, and a mutual next-step decision at the end. Avoid leading with a product tour.
Five illumination questions
Adapt these to the buyer's words and let answers determine follow-ups:
- How does this workflow work today, and where does it break down?
- What happens when that breaks, and who feels the impact?
- What have you tried, and what stopped that from solving it?
- What changed that makes this worth addressing now?
- How would you decide whether a pilot worked, and who would need to approve it?
Follow with funding, timing, access, volume, baseline, and implementation questions only where missing answers affect fit. Ask how the buyer estimates the cost rather than inventing revenue loss. A title is not proof of purchasing authority. Record both the user of the workflow and the approver.
Summarize what you heard and invite correction before connecting an offer to the problem. If there is no material pain, feasible funding path, priority, or deliverable fit, explain the mismatch and suggest a clean exit. Avoid overcoming a real disqualifier with more persuasion.
Close for a mutual next step
For a fit, name the next event, purpose, attendees, owner, date/time, and prerequisite. A proposal should answer a decision already understood. If another stakeholder is required, propose a joint review and ask what they need to decide. Do not treat "I'll send something" as progress.
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 · 57 lines · 52 tokens per session scan A fb2cfee55e7e
sales-discovery-call-coach is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 894 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…