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 olelehmann1337/workshop-plugin --skill landingpage-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/landingpage-workshop-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/landingpage-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/landingpage-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.1 | $0.00128 | $0.04052 |
| Opus 5 | $0.00064 | $0.02026 |
| Sonnet 5 | $0.00026 | $0.00810 |
| Haiku 4.5 | $0.00013 | $0.00405 |
Grade A, and why
landingpage-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 8d 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Page Builder
Most sales pages fail because people write them top to bottom. They start with the headline, get stuck, and quit. Or they copy a template and end up with generic copy that sounds like everyone else.
The trick is writing in the wrong order. You write the story first (it finds the voice), then the offer, then the close, then the lead, and the headline dead last — because by then you actually know what you're selling and why it matters.
This skill builds a complete sales page using that backwards process.
the core job
Produce a complete sales page with all 5 sections:
- Headline (prehead + main headline + deck copy)
- Lead (150–200 word teaser)
- Story (credibility through narrative)
- Offer (what they get, broken into components)
- Close (price justification + guarantee + CTA + FAQ)
Output: Full sales page copy, assembled in reading order, ready to paste into a page builder.
before starting: gather context
STOP. Do not write any copy 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.mdinto this conversation. Scan for:- Business — what the user sells, pricing tiers, delivery model, current proof. Grounds the offer and price sections in reality.
- ICP — who the customer is, their pain, objections, the exact phrases they use. The headline, lead, and story must speak to THIS person.
- Voice — do/don't rules, tone, sample sentences. Every section must read like the user wrote it.
- If missing, check the project folder for
Context/business.md,Context/icp.md,Context/voice.mdat the project root. Read whichever exist. - If voice is still missing: note it and proceed — the draft will be generic-tone. The user can pass the output through
/anti-slopor paste voice samples inline.
Step B: Confirm the brief (≤2 questions, combined)
Skip anything CLAUDE.md or Context/ files already cover. Combine related inputs into at most 2 questions:
What ships with it
6 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.
- 8d ago First seen · 377 lines · 128 tokens per session scan A e211aab1c83c
landingpage-workshop-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 128 tokens to every session and 4,052 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.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…