content-blog

content-blog is a skill for Claude Code, Codex from vstorm-co/content-skills. It costs 45 tokens per session (1,449 once invoked), scanned A, original, MIT.

A writing guide for producing long blog posts, such as tutorials, opinion pieces, case studies, list articles, and detailed analyses.

In plain words
What is it for?
It helps plan and write articles using a brand voice, a chosen format, supplied facts, links, key points, and a target length.
Why use it?
It removes the need to invent a structure and tone from scratch while helping avoid vague, generic writing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps plan and write articles using a brand voice, a chosen format, supplied facts, links, key points, and a target length.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vstorm-co/content-skills/content-blog
Install

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.

Any agent
npx skills add vstorm-co/content-skills --skill content-blog
Clone the repo
git clone --depth 1 https://github.com/vstorm-co/content-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for content-blog

README.md
[![agentmods](https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-blog/github.svg)](https://agentmods.dev/skills/vstorm-co/content-skills/content-blog)
Your own site
<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-blog"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-blog/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.

agentmods 80×15 button for content-blog

Your own site · 80×15
<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-blog"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.01449
Opus 5 $0.00023 $0.00724
Sonnet 5 $0.00009 $0.00290
Haiku 4.5 $0.00005 $0.00145

Measured 12d ago against content hash ec0942bae7b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

content-blog 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 12d 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.

skills/content-blog/SKILL.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blog Post Generation

Before You Start

  1. Check for brand voice: Read brand/VOICE.md if it exists. This file defines the brand's tone, vocabulary, formality level, and signature patterns. If it does not exist, use sensible defaults (clear, direct, conversational-professional) and suggest the user run the content-setup skill to configure their voice.

  2. Determine the post type: Ask the user (or infer from their prompt) which format fits best:

    • Tutorial -- step-by-step how-to content (templates/tutorial.md.template)
    • Opinion -- thought-leadership or contrarian takes (templates/opinion.md.template)
    • Case Study -- results-driven narrative (templates/case-study.md.template)
    • Listicle -- list-format posts with substance (templates/listicle.md.template)
    • Deep Dive -- long-form technical analysis (templates/deep-dive.md.template)
  3. Gather inputs: Title or topic, target audience, key points the user wants covered, desired word count range, any links or data to reference.


Generation Flow

Follow these five stages. Do not skip any.

Stage 1: Brief

Confirm the following with the user (or extract from their prompt):

  • Topic and angle
  • Target audience and their existing knowledge level
  • Post type (tutorial, opinion, case-study, listicle, deep-dive)
  • Key points or arguments to include
  • Desired length (short: 800-1200 words, medium: 1200-2000 words, long: 2000-3500 words)
  • CTA or desired reader action

Stage 2: Outline

Produce a structured outline with:

  • Working title (can be refined later)
  • Hook concept (one sentence describing how the post opens)
  • Section headings with 2-3 bullet points each describing what goes in that section
  • Closing approach (CTA, insight, question, callback to opening)

Present the outline to the user for approval before drafting.

Stage 3: Draft

Write the full post following the approved outline. Apply:

  • The appropriate template from templates/
  • Brand voice from brand/VOICE.md (see voice-integration.md)
  • Anti-slop rules from anti-slop.md
  • Concrete examples, data, and specifics over abstract claims

Read the full file on GitHub · 157 lines

Files

What ships with it

7 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.

Changes

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.

  1. 12d ago First seen · 157 lines · 45 tokens per session scan A ec0942bae7b1

Subscribe to this mod's changes

content-blog is a skill published in the GitHub repository vstorm-co/content-skills (22 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,449 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.