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 first-client-90-day-plangit 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/first-client-90-day-plan)<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/first-client-90-day-plan"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/first-client-90-day-plan/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/first-client-90-day-plan"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/first-client-90-day-plan.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.00054 | $0.01232 |
| Opus 5 | $0.00027 | $0.00616 |
| Sonnet 5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
first-client-90-day-plan 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Client in 90 Days
Turn the user's skills, access to buyers, and available hours into a path toward a first paid engagement. Start with the earliest unproven sales step and produce the asset needed to test it today. Do not make a beginner finish a course before talking to buyers.
Establish the starting point
Find the lane (freelancer, agency, or internal operator), start date, weekly sales hours, delivery capability, existing buyer access, proof, current opportunities, and desired engagement. Separate the seller's lane from the buyer's role. Default to a first paid pilot with a bounded scope when a recurring service is unproven. Use a retainer only when ongoing work creates ongoing value.
Define success before planning: for an external sale, signed scope plus the agreed first payment actually received; record contract and payment evidence separately. For an operator, named sponsor approval, resources, success metric, and a pilot start date. A friendly reply, scheduled call, verbal yes, proposal, or unpaid demo is an intermediate event.
Build an evidence-gated calendar
Use these overlapping windows as a starting schedule. Adjust for the user's capacity and existing evidence; never restart validated work just to follow the calendar.
| Window | Work and concrete output | Evidence to advance |
|---|---|---|
| Days 1-7 | One ICP sentence, five disqualifiers, ten buyer conversations | Repeated pain, ability to fund, reachable decision path; otherwise rewrite or reject |
| Days 8-14 | One offer paragraph, bounded deliverables and risk reversal | Three real say-it-back reactions; feasible delivery and explicit unknowns |
| Days 15-30 | One primary channel, 25-50 sourced prospects, first small outreach test | Relevant replies and a buyer-confirmed qualified meeting; log actual counts |
| Days 31-60 | Discovery, costed pilot, pricing discussion, follow-up | Buyer-confirmed problem, decision process, and a dated next step |
| Days 61-90 | Close suitable opportunities, deliver a first win, review ongoing needs | Paid engagement and agreed acceptance evidence; retainer only if justified |
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 · 63 lines · 54 tokens per session scan A 1b0e79de3cbd
first-client-90-day-plan is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 1,232 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…