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 newsletter-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/newsletter-workshop-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/newsletter-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/newsletter-workshop-v2/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/olelehmann1337/workshop-plugin/newsletter-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/newsletter-workshop-v2.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.00074 | $0.05414 |
| Opus 5 | $0.00037 | $0.02707 |
| Sonnet 5 | $0.00015 | $0.01083 |
| Haiku 4.5 | $0.00007 | $0.00541 |
Grade A, and why
newsletter-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 9d 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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter Writer
Most newsletters read like blog posts with a subscribe button. Stiff, educational, forgettable. The ones people actually forward sound like a letter from a smart friend who happened to learn something worth sharing.
This skill turns raw ideas into newsletters that feel personal and hit hard — using proven frameworks for angles, structure, and momentum.
IMPORTANT: All output from this skill must follow the anti-slop editing rules. Run the antislop-workshop skill as a final pass on every newsletter before presenting it. Zero tolerance for AI-sounding copy.
the core job
Produce a complete newsletter edition that:
- Follows the Rule of One (one problem, one story, one solution, one CTA)
- Opens with a hook that earns the next sentence
- Sounds like a person wrote it, not a content machine
- Ends with a line worth remembering
Output: Subject line + full newsletter + P.S. — ready to send.
before starting: gather context
STOP. Do not write a newsletter until context is in hand AND the core idea is clear. 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, current launches, proof. Grounds takes in reality.
- ICP — who the reader is, their pain, exact phrases. The newsletter must sound written TO this person.
- Voice — tone, do/don't, sample sentences. Must read like the user wrote it.
- 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, combined)
Skip anything context already covers. Combine into at most 2 questions:
- Raw material + core idea — "What are we working with (voice memo, notes, starting fresh?), and what's the ONE point? Not three — one." (If unclear, help them find it.)
- CTA + opener style — "What should the reader do (reply/click/buy/think differently?) and want a Snapshot opener (scene with time/sensory) or a Snipershot (direct hook)?"
What ships with it
2 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.
- 9d ago First seen · 514 lines · 74 tokens per session scan A 29762c853c82
newsletter-workshop-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 5,414 once invoked, about $0.0004 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…
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…
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…