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 agentmods add commands/brainbytes-dev/everything-claude-marketing/content-calendargit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWrote 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/commands/brainbytes-dev/everything-claude-marketing/content-calendar)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-marketing/content-calendar"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-marketing/content-calendar.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.01476 |
| Opus 5 | $0.00013 | $0.00738 |
| Sonnet 5 | $0.00005 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00148 |
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 3d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/content-calendar
Plan a strategic editorial content calendar that maps topics, formats, and publishing cadence to your business objectives.
What This Command Does
This command creates a comprehensive content calendar that goes beyond a simple list of topics and dates. It starts by understanding your business goals, audience segments, and key themes, then builds a structured publishing plan that balances thought leadership, demand generation, SEO, and community content. The calendar includes topic ideas with working titles, recommended formats (blog, video, podcast, social, newsletter), distribution channels, ownership assignments, and a realistic publishing cadence. It also maps content to funnel stages and identifies content gaps.
When to Use
- Planning quarterly or monthly editorial strategy from scratch
- Revamping an underperforming content program
- Launching a new blog, newsletter, podcast, or video series
- Preparing content around a product launch, event, or campaign
- Aligning content across multiple teams or contributors
- Building a content engine for SEO and organic growth
- Coordinating content across formats and channels
How It Works
- Understands objectives — Asks about business goals, target audience, key themes, and existing content assets
- Audits the landscape — Considers your competitive positioning, seasonal trends, and industry events
- Defines content pillars — Establishes 3-5 thematic pillars that align with your expertise and audience needs
- Maps the funnel — Ensures content exists for awareness, consideration, and decision stages
- Builds the calendar — Creates a week-by-week or day-by-day schedule with topics, formats, channels, and owners
- Sets the cadence — Recommends a sustainable publishing frequency based on your resources
- Plans distribution — Maps each piece to primary and secondary distribution channels
- Identifies dependencies — Flags content that needs design assets, subject matter experts, or customer participation
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.
- 3d ago First seen · 138 lines · 26 tokens per session scan A 4003aaf8e62d
content-calendar is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 1,476 once invoked, about $0.0001 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-31.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
sync-linear
Sync current work with Linear ticket status.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.