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 weekly-sales-loopgit 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/weekly-sales-loop)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/weekly-sales-loop"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/weekly-sales-loop/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/weekly-sales-loop"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/weekly-sales-loop.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.00050 | $0.00946 |
| Opus 5 | $0.00025 | $0.00473 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
weekly-sales-loop 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Sales Loop
Make selling fit the user's actual week. Produce three named blocks and a small scorecard that distinguishes real progress from a full-looking CRM.
Fit the routine to capacity
Use the chosen ICP/channel, current workload, working days/timezone, weekly sales time, live opportunities, and historical counts. If time is unknown, propose a clearly labeled starter schedule rather than assuming daily hours the user does not have.
Create List Build, Work-the-List, and Reply Triage blocks. Reserve a brief same-working-day triage window before allocating remaining time between research and outreach. Include call preparation, actual calls, and review time in the total. State duration and purpose for every block and verify that the total fits the available hours. For an operator, use stakeholder mapping, sponsor conversations, and decision follow-through.
Work-the-List includes individualized initial outreach and due follow-ups to eligible prospects. Reply Triage stops sequences on replies, handles interested buyers, clarifies concerns, respects later/no requests, and records the next step. Do not schedule unapproved sends or modify a calendar unless execution is requested.
Define and reconcile the scorecard
Capture a reporting period, timezone, and cohort. The core deck scorecard is sent / replied / booked. Expand only enough to diagnose the user's bottleneck:
Period | Qualified prospects added | Unique people first contacted | Message touches | Unique replies | Positive replies | Booked | Held | Qualified opportunities | Proposals | Signed | Paid
Track next owner, action, and date for active opportunities. Reconcile duplicates, reschedules, cancellations, and deals that started before the period. All-time pipeline stock is not this week's conversion cohort. Separate a booking created this week from a meeting held this week.
For a defined first-contact cohort, reply rate = unique repliers / unique contacted people; booking rate = unique booked prospects / unique contacted people. Report sample size and maturation window. If the denominator is missing or zero, show N/A and raw counts. Do not infer performance from tiny immature cohorts or treat repeated touches as new prospects.
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 · 60 lines · 50 tokens per session scan A bc0a82e2eb77
weekly-sales-loop is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 946 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…