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 agentmods add skills/olelehmann1337/workshop-plugin/emailsequence-workshop-v2npx skills add olelehmann1337/workshop-plugin --skill emailsequence-workshop-v2git clone --depth 1 https://github.com/olelehmann1337/workshop-pluginWhat 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 | $0.00130 | $0.04396 |
| Opus 5 | $0.00065 | $0.02198 |
| Sonnet 5 | $0.00026 | $0.00879 |
| Haiku 4.5 | $0.00013 | $0.00440 |
Grade A, and why
emailsequence-workshop-v2 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequence Builder
Subscribers are cheap. Customers are expensive. The gap between "signed up" and "paid" is a graveyard of abandoned inboxes and ignored autoresponders. Most people either blast sales emails too early or send so much free content they never ask for the sale. This skill builds the path from opt-in to purchase — step by step, email by email — and refuses to ship a draft that hasn't been grounded in the reader's actual voice and pain.
the core job
Produce a complete, ready-to-load email sequence that moves someone from new subscriber to paying customer without torching the relationship along the way.
Every sequence ships with subject lines, preview text, full written copy, send timing, and one CTA per email.
Output: A single markdown deliverable in the format defined under ## output format, ready to paste into the user's email tool (ConvertKit, Beehiiv, Kit, ActiveCampaign, etc.).
before starting: gather context
STOP. Do not write a single email until context is in hand. Cap your brief-confirmation at 2 questions max.
Step A: Gather context (fast)
- Check CLAUDE.md first. Claude auto-loads
~/.claude/CLAUDE.mdand any project-levelCLAUDE.md. Scan for:- Business — what the user sells, pricing. Grounds the paid offer and bridge.
- ICP — who the subscriber is, their pain, exact phrases. Subject lines must sound written for THIS person.
- Voice — tone, do/don't rules, sample sentences. Emails must read like the user wrote them.
- If missing, check the project folder for
Context/business.md,Context/icp.md,Context/voice.md. Read whichever exist.
Step B: Confirm the brief (≤2 questions)
Skip everything CLAUDE.md and Context/ files already cover. Then ask AT MOST 2 questions from this priority list:
| Priority | Input | Question | Why it matters |
|---|---|---|---|
| 1 | Freebie + bridge | "What did they sign up for, and how does it connect to what you're selling?" (combine into one question) | Shapes email 1 and makes the pitch feel natural |
| 2 | Paid offer + price | "What are you selling them and at what price?" (combine) — skip if business context covers it | Determines pitch intensity and trust-building length |
| 3 | Blockers | "Top 1-2 reasons they might NOT buy?" — skip if ICP context covers it | Shapes objection-handling emails |
What ships with it
4 files 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 · 384 lines · 130 tokens per session scan A 2253384c9e1b
emailsequence-workshop-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 130 tokens to every session and 4,396 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…