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 vstorm-co/content-skills --skill content-bloggit clone --depth 1 https://github.com/vstorm-co/content-skillsWrote 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/vstorm-co/content-skills/content-blog)<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.
<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>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.00045 | $0.01449 |
| Opus 5 | $0.00023 | $0.00724 |
| Sonnet 5 | $0.00009 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
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.
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
-
Check for brand voice: Read
brand/VOICE.mdif 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. -
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)
- Tutorial -- step-by-step how-to content (
-
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(seevoice-integration.md) - Anti-slop rules from
anti-slop.md - Concrete examples, data, and specifics over abstract claims
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.
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.
- 12d ago First seen · 157 lines · 45 tokens per session scan A ec0942bae7b1
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.
Other skills, from other repositories
frame-logo-outro
Segmented logo assembly, glow bloom, and tagline reveal for video outros or brand closing frames.
steadyagent-workflow
Local-first Codex workflow for planning, debugging, reviewing, refactoring, improving AGENTS.md, building skills, publishing agent harness repositories, or running complex multi-step coding tasks that need staged diagnosis, context control, verification loops, review strategy, release evidence, and…
ackit-workflow
Enforce the ACKit docs-first, task-first workflow with one active checklist item and evidence-based completion.
ackit-policy-authoring
Author layered ackit policy files with deterministic merge, scoping and lockable rules.
ackit-context-optimization
Build budgeted context packs and trim instruction bloat for coding agents.
ackit-scan-and-fix
Run ACKit scan, interpret findings by severity, and apply safe fixes with suppression hygiene.