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 contentgit 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)<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content/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"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content.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.00141 | $0.03609 |
| Opus 5.5 | $0.00056 | $0.01444 |
| Sonnet 5.5 | $0.00028 | $0.00722 |
| Haiku 4.5 | $0.00014 | $0.00361 |
Grade A, and why
content 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Studio — Main Router
This is the orchestrator skill for the content-skills pack. It receives /content <subcommand> invocations and delegates to the correct sub-skill. It does not generate content itself — it routes, enforces brand consistency, and coordinates multi-step workflows.
The pack is organized around a shared brand system. Every sub-skill reads from the same brand configuration, so voice, tone, visual identity, and audience targeting stay consistent whether the user is writing a blog post, drafting a LinkedIn update, or building a slide deck.
Skill Pack Structure
content-skills/
├── content/SKILL.md ← you are here (main router)
├── brand/ ← shared brand source of truth
│ ├── BRAND.md ← core identity: name, tagline, audience, positioning
│ ├── VOICE.md ← voice & tone rules, vocabulary, banned phrases
│ ├── VISUAL.md ← colors, typography, logo usage, visual style
│ ├── assets/ ← brand asset files
│ ├── fonts/ ← typeface files
│ ├── logo/ ← logo variants
│ ├── palettes/ ← color palette definitions
│ └── voice-samples/ ← reference writing samples
├── skills/ ← individual content sub-skills
│ ├── content-setup/ ← brand setup & voice profiling
│ ├── content-strategy/ ← strategy, planning, briefs
│ ├── content-blog/ ← long-form blog posts
│ ├── content-twitter/ ← X/Twitter threads & posts
│ ├── content-linkedin/ ← LinkedIn posts & articles
│ ├── content-reddit/ ← Reddit posts & comments
│ ├── content-hackernews/ ← Hacker News posts
│ ├── content-presentation/ ← Slidev/Reveal/Spectacle decks
│ ├── content-infographic/ ← data visualizations & infographics
│ ├── content-image/ ← image generation prompts
│ ├── content-video/ ← Remotion video scripts
│ ├── content-calendar/ ← editorial calendar management
│ ├── content-repurpose/ ← cross-platform content adaptation
│ └── content-audit/ ← content quality scoring & audits
├── agents/ ← agent definitions for parallel workflows
├── scripts/ ← utility scripts
├── styles/ ← shared style assets
└── assets/ ← shared asset files
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 · 299 lines · 141 tokens per session scan A 8602ae7de674
content is a skill published in the GitHub repository vstorm-co/content-skills (26 stars, last pushed 6mo ago), licensed MIT. It adds 141 tokens to every session and 3,609 once invoked, about $0.0006 per session on Opus 5.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
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-context-optimization
Build budgeted context packs and trim instruction bloat for coding agents.
ackit-policy-authoring
Author layered ackit policy files with deterministic merge, scoping and lockable rules.
ackit-scan-and-fix
Run ACKit scan, interpret findings by severity, and apply safe fixes with suppression hygiene.
agents-doctor
Validate AGENTS.md and related agent instruction files with the published agents-doctor CLI. Use when the user asks to check, lint, verify, explain, audit, fix, release-check, or compare AGENTS.md, CLAUDE.md, GEMINI.md, agent instruction inheritance, tool profiles, context fidelity, instruction graphs, GitHub…