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 interesting-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/interesting-workshop-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/interesting-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/interesting-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/interesting-workshop-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/interesting-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.00109 | $0.05045 |
| Opus 5.5 | $0.00044 | $0.02018 |
| Sonnet 5.5 | $0.00022 | $0.01009 |
| Haiku 4.5 | $0.00011 | $0.00505 |
Grade A, and why
interesting-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 1mo 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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Sharpener
Most content fails because it tells people what they already believe. Nobody shares "yep, that's what I thought." They share "holy shit, I never thought of it that way." This skill exists to manufacture that second reaction on demand — by treating "interesting" as a craft, not a vibe.
The position this skill takes: interesting isn't a personality trait, it's a structural property. Murray Davis proved an idea is interesting when it denies one specific thing the audience assumes is true. Get the assumption right, deny it the right way, deliver it with the right technique — and "interesting" becomes reproducible.
the core job
Take a bland or generic idea and produce 3-5 reworked versions, each pairing a Murray Davis proposition type (the angle) with a novelty technique (the delivery). Every version must deny one specific audience assumption and survive a stress-test for substance.
Output format: A markdown brief listing 3-5 angles. Each angle includes proposition type, the assumption it denies, the novelty technique used, the rewritten idea ready to use as a hook/post/headline, and a one-line "why it works." Ends with a "strongest option" recommendation.
before starting: gather context
STOP. Do not produce angles until voice is in hand AND the brief is confirmed. Cap questions at 2.
Step A: Gather voice context (fast)
This skill only needs one thing from context: voice. Audience and topic come from the brief.
- Check CLAUDE.md first. Claude auto-loads
~/.claude/CLAUDE.mdand any project-levelCLAUDE.md. Scan for do/don't rules, tone, sample sentences. - If missing, check the project folder for
Context/voice.md. Read if present. - If voice is still missing: note it and proceed. Angles will be generic-tone; the user can pass the output through
/anti-slopor paste voice rules inline.
Step B: Confirm the brief (≤2 questions, combined)
Combine into at most 2 questions:
- Idea + audience — "What's the idea/topic, and who needs to find it interesting?" (one question, two halves)
- Format — tweet, newsletter, headline, talk, landing page — delivery changes length and rhythm.
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.
- 1mo ago First seen · 388 lines · 109 tokens per session scan A 6e2e7b5fa727
interesting-workshop-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 6mo ago), licensed MIT. It adds 109 tokens to every session and 5,045 once invoked, about $0.0004 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…