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-calendargit 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-calendar)<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-calendar"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-calendar/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-calendar"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-calendar.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.00036 | $0.01602 |
| Opus 5 | $0.00018 | $0.00801 |
| Sonnet 5 | $0.00007 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
content-calendar 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Calendar Planning
Before You Start
-
Check for brand context: Read
brand/VOICE.mdif it exists. Calendar planning should align content themes with brand pillars. If the user has already run the content-strategy skill, reference the content pillars and briefs from that output. -
Determine the calendar type: Ask the user (or infer from their prompt) what kind of planning they need:
- Monthly Calendar -- a full month of content planned across platforms (
templates/monthly-calendar.md.template) - Campaign Plan -- a focused burst of content around a single theme, launch, or event (
templates/campaign-plan.md.template) - Content Series -- a connected sequence of content pieces published over time (
templates/content-series.md.template)
- Monthly Calendar -- a full month of content planned across platforms (
-
Gather inputs: Platforms the user publishes on, existing content pillars, any fixed dates (launches, events, holidays), production capacity (how much content per week is realistic), and current content pipeline.
Planning Flow
Stage 1: Context Gathering
Understand the constraints before scheduling anything:
- Platforms: Which platforms does the user publish on? Each has different cadence norms. See
cadence-guide.md. - Capacity: How many pieces per week can the team realistically produce? Be honest -- overplanning leads to burnout and abandoned calendars.
- Pillars: What content pillars exist? Reference
brand/BRAND.mdor the output of the content-strategy skill if available. If no pillars are defined, suggest 3-5 based on the user's context. - Fixed dates: Product launches, conferences, holidays, seasonal events, industry milestones.
- Existing pipeline: Content already in progress, scheduled, or published recently. Avoid redundancy.
Stage 2: Cadence Design
Set the publishing cadence for each platform based on:
- Platform norms: See
cadence-guide.mdfor recommended frequencies. - Team capacity: Never exceed what the team can sustain. A calendar that collapses after two weeks is worse than a modest calendar maintained for six months.
- Content quality threshold: Reduce cadence before reducing quality. One great post per week beats five mediocre posts.
- Audience expectations: If you have trained your audience to expect a weekly newsletter, do not suddenly go monthly.
What ships with it
4 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 · 145 lines · 36 tokens per session scan A 3f7aec054b8e
content-calendar is a skill published in the GitHub repository vstorm-co/content-skills (22 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,602 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.