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-follow-up-plannergit 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-follow-up-planner)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/sales-follow-up-planner"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-follow-up-planner/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-follow-up-planner"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/sales-follow-up-planner.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.00048 | $0.00832 |
| Opus 5 | $0.00024 | $0.00416 |
| Sonnet 5 | $0.00010 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
sales-follow-up-planner 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Follow-up Planner
Keep a legitimate deal moving with relevant next steps. Start from the actual thread and commitments. Do not imply that silence means interest or rejection with certainty.
Classify the thread
Use the last messages and dates, stage, buyer's stated pain, outstanding question, promised next step, explicit timing, and prior attempts. Distinguish an unread cold opener, an active evaluation, a waiting-on-approver deal, a requested future check-in, and a closed/no-contact thread.
If the buyer said no or asked not to be contacted, close the sequence. A restart requires new permission or an appropriate inbound request. If they named a future date, respect it. An absent thread means a generic template, not fabricated relationship context.
Build a finite sequence
Prefer a few useful touches with a stated final attempt. As a configurable default for an open deal with no agreed schedule, suggest a relevant recap, a new useful clarification a few business days later, and a respectful close-out roughly a week after that. Explain that timing is a proposed operating choice, not a published educator rule. Override it with the buyer's commitments and context.
Every touch needs a purpose: answer an open concern, share a relevant artifact, simplify a decision, or clarify whether to close the loop. Do not write "just checking in", guilt, fake urgency, invented case studies, or claims that the prospect consumed content without evidence.
Write actual drafts using the supplied facts. For each give intended date or trigger, new value, single question, and the event that cancels the next touch. Stop the sequence on any reply and handle its content before planning another send. Do not move to another channel to bypass a refusal.
A soft close-out should allow a no: "Would you prefer I close this out for now? Happy to revisit if [their real trigger] changes." Do not presume the trigger if unknown.
For a dormant lead, identify a relevant new event or an agreed revisit date. Do not schedule an automatic generic revival of every silent contact. For an internal operator, tie reminders to the sponsor's decision or resource milestone.
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 · 50 lines · 48 tokens per session scan A 405925a45fed
sales-follow-up-planner is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 832 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-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…