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/cdeistopened/skill-stack/skill-stack-newsletter-writernpx skills add cdeistopened/skill-stack --skill skill-stack-newsletter-writergit clone --depth 1 https://github.com/cdeistopened/skill-stackWrote 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/cdeistopened/skill-stack/skill-stack-newsletter-writer)<a href="https://agentmods.dev/skills/cdeistopened/skill-stack/skill-stack-newsletter-writer"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/skill-stack-newsletter-writer.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.00041 | $0.00939 |
| Opus 5 | $0.00020 | $0.00469 |
| Sonnet 5 | $0.00008 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
skill-stack-newsletter-writer 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Stack Newsletter Writer
This skill handles newsletter FORMAT only. Writing style comes from the root writing-style skill.
Newsletter Structure
Frontmatter Schema
---
title: "[Skill Name]"
issue: [number]
date: "YYYY-MM-DD"
skill: [skill-slug]
thumbnail: "/images/thumbnails/[slug].png"
description: "[SEO description: 150-160 chars, keyword + insight + deliverable]"
tags: ["tag1", "tag2", "tag3"]
---
Field Notes:
title: The skill name, clean. No subtitles like "The X That Changed Y"skill: Maps to the downloadable skill package slugthumbnail: Risograph style (see image-prompt-generator)description: SEO-optimized but punchy (see writing-style for guidelines)tags: 3-5 relevant keywords, lowercase
Content Sections
Each newsletter follows this rhythm:
1. Opening Hook (150-200 words)
Personal story or observation. Ground the reader in something real before introducing the skill concept.
- Specific place, time, sensory detail
- Something you found, discovered, encountered
- The seed that led to the insight
No throat-clearing. Start in media res.
2. The Discovery (100-150 words)
Bridge from story to skill. The moment you understood something about how this works.
- "Fast forward..."
- "Here's what I discovered..."
- A single key insight, stated directly
3. Core Mechanism (200-300 words)
Explain HOW the skill works. This is the teaching section.
- What most people get wrong
- The counterintuitive insight
- Concrete examples (actual prompts, actual output)
Use section break (---) not headers here. Let prose flow.
4. The Wizard/Workflow (100-150 words)
Walk through how to use it. Conversational but specific.
- Step 1, step 2, step 3
- What the user does at each stage
- What they get at the end
5. Skill Package (formatted block)
Always include this exact structure:
**The skill package includes:**
- `SKILL.md` — [Brief description]
- `WIZARD.md` — [Brief description]
- `templates/` — [Brief description]
- `references/` — [Optional: examples, samples]
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 · 173 lines · 41 tokens per session scan A 2ae9c98393e4
skill-stack-newsletter-writer is a skill published in the GitHub repository cdeistopened/skill-stack (27 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 939 once invoked, about $0.0002 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-30.
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…