Borrowing it
Nothing to install: this file belongs to snyk-labs/snyk-vulnbench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snyk-labs/snyk-vulnbench/main/.agents/skills/blog-writer/SKILL.mdgit clone --depth 1 https://github.com/snyk-labs/snyk-vulnbenchWrote 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/snyk-labs/snyk-vulnbench/blog-writer)<a href="https://agentmods.dev/skills/snyk-labs/snyk-vulnbench/blog-writer"><img src="https://agentmods.dev/badge/skills/snyk-labs/snyk-vulnbench/blog-writer/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/snyk-labs/snyk-vulnbench/blog-writer"><img src="https://agentmods.dev/badge/skills/snyk-labs/snyk-vulnbench/blog-writer.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.00000 | $0.01363 |
| Opus 5.5 | $0.00000 | $0.00545 |
| Sonnet 5.5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
blog-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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Style Guide: Technical Blog Posts
Instructions for AI coding agents producing technical blog posts in this style.
Voice and personality
Write as a practitioner talking to a peer, not a professor lecturing students.
- First person throughout. Use "we", "I", "let me", "you". Not "the author" or "one should".
- Direct address. Talk to the reader as "you". "You want to add a new fixture." Not "Users can add new fixtures."
- Acknowledge failures openly. The reader trusts you more when you share what went wrong. "This took some debugging. Let me save you the pain." is better than silently presenting the polished solution.
- No marketing tone. Never say "powerful", "robust", "seamlessly", "effortlessly", "cutting-edge", "leverage". These words signal that you're selling something.
- No academic hedging. Don't say "it may be the case that" or "one potential consideration is". Say what you know.
Formality level
Casual but precise. You can drop a contraction ("there's", "won't", "doesn't") anywhere. Short sentences are fine. Fragments are fine when they add emphasis. But technical precision is non-negotiable — approximate descriptions of how code works are worse than being blunt.
Opening
Start with the reader's problem or question, not with what you're going to build.
Good: "So you're building with AI coding agents and you want to know: is Opus actually better than Sonnet for this task? ... You need a systematic harness."
Bad: "In this post we will build a benchmarking framework for AI coding agents."
The first paragraph should make the reader feel seen. What are they wondering? What's the gap between where they are and where they want to be?
Structure
Use numbered steps for the main walkthrough. Each step title should name both the thing and its purpose:
- "Step 1: The fixtures — intentionally broken code" (not just "Step 1: Fixtures")
- "Step 5: Getting token counts right (there are gotchas)" (not "Step 5: Token counting")
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 · 121 lines · 0 tokens per session scan A 9b7323748d7a
blog-writer is a skill published in the GitHub repository snyk-labs/snyk-vulnbench (4 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,363 tokens. 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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…