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/articlewriter-v2npx skills add olelehmann1337/workshop-plugin --skill articlewriter-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/articlewriter-v2)<a href="https://agentmods.dev/skills/olelehmann1337/workshop-plugin/articlewriter-v2"><img src="https://agentmods.dev/badge/skills/olelehmann1337/workshop-plugin/articlewriter-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.00182 | $0.03403 |
| Opus 5 | $0.00091 | $0.01702 |
| Sonnet 5 | $0.00036 | $0.00681 |
| Haiku 4.5 | $0.00018 | $0.00340 |
Grade A, and why
articlewriter-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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article Writer (X/Twitter)
Most X articles die because they read like blog posts that accidentally ended up on Twitter. Dense paragraphs, no numbered steps, no copy-paste material, a "conclusion" that tells the reader what they just read.
The X articles that get passed around feel like a smart friend texted you a walkthrough. Numbered steps. Exact prompts you can copy. An analogy that makes the concept click. A direct "go do this right now" at the end.
This skill writes that.
the core job
Produce a publish-ready X/Twitter article that:
- Opens with a hook that pays off in 2-4 sentences
- Walks the reader through an exact process they can copy
- Includes at least one copy-paste block (prompt, command, template)
- Lands with a direct push to take action
- Sounds like the user wrote it, not a content machine
Output: Full article in plain markdown, ready to paste into X's article editor.
before starting: gather context
STOP. Do not write 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:- Voice — tone, do/don't rules, sample sentences. The article must read like the user wrote it.
- Audience / ICP — who the reader is, what they want, their vocabulary.
- Brand + CTA — name, newsletter link, product, free asset they give away. Goes into the P.S. blocks.
- If missing, check the project folder for
Context/voice.md,Context/icp.md,Context/business.md. Read whichever exist. - If voice is still missing: flag it — "Voice samples are missing. I'll write in a neutral direct tone; paste 3-5 sentences in your voice to get a true match."
Step B: Confirm the brief (≤2 questions, combined)
Skip anything context already covers. Combine into at most 2 questions:
- Topic + skeleton — "What's the article about, and is this a Tutorial (here's how to set up / build X) or a Breakdown (here's what's new + what to do about it)?"
- Personal result or news hook — "Do you have a specific result, number, or recent news that anchors this? (e.g. 'I went from X to Y in Z weeks' or '[Tool] just dropped [feature]')"
What ships with it
3 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 · 286 lines · 182 tokens per session scan A 069c27d70154
articlewriter-v2 is a skill published in the GitHub repository olelehmann1337/workshop-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 182 tokens to every session and 3,403 once invoked, about $0.0009 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…