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/leadmagnet-workshop-v2npx skills add olelehmann1337/workshop-plugin --skill leadmagnet-workshop-v2git clone --depth 1 https://github.com/olelehmann1337/workshop-pluginWrote 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/olelehmann1337/workshop-plugin/leadmagnet-workshop-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/leadmagnet-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/leadmagnet-workshop-v2.svg" alt="Measured on agentmods" 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 | $0.00119 | $0.05844 |
| Opus 5 | $0.00060 | $0.02922 |
| Sonnet 5 | $0.00024 | $0.01169 |
| Haiku 4.5 | $0.00012 | $0.00584 |
Grade A, and why
leadmagnet-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 4d 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Magnet Generator
Your prospect doesn't care about your freebie. They care about the problem eating at them right now. The best lead magnets solve that problem fast and leave them wanting the full solution you sell. Most lead magnets fail because they're built around what the seller wants to give away instead of step 1 of a journey toward what they actually sell.
This skill builds lead magnet concepts that pull their weight as the first chapter of the paid offer — and, when asked, drafts the actual content inside the magnet.
the core job
Produce 3-5 distinct lead magnet concepts the user can pick from, each with a clear angle, format choice, and connection to their paid product. When the user explicitly requests it, also produce the full content inside the chosen magnet (PDF body, quiz questions, challenge emails, checklist, etc.).
Every business has multiple valid approaches. The job is finding which one fits their audience, model, and offer best — then optionally executing on the chosen one.
Output format — concept deliverable:
| Element | What it covers |
|---|---|
| Concept | What the lead magnet is, in one sentence |
| Format | Quiz, PDF, calculator, challenge, template, etc. |
| Angle | Why someone would hand over their email for this |
| Path to paid | How consuming this naturally leads to wanting the full offer |
| Build notes | Difficulty level and resources required |
Output format — content deliverable (when requested):
The actual lead magnet itself: title, intro/promise, full body content broken into named sections, and a soft CTA bridge to the paid offer.
before starting: gather context
STOP. Do not produce lead magnet concepts or content until context is in hand. Cap questions at 2 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, the paid offer the magnet bridges to.
- ICP — audience pain, their phrases. The promise must solve a pain they have TODAY.
- Voice — tone, do/don't. The magnet title and landing copy must sound like the user.
- If missing, check the project folder for
Context/business.md,Context/icp.md,Context/voice.md. Read whichever exist. - If audience is still unclear after both: ask inline — a lead magnet without an ICP is just a free PDF nobody wants.
What ships with it
5 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.
- 4d ago First seen · 461 lines · 119 tokens per session scan A 50151245895a
leadmagnet-workshop-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 5,844 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…