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 brainbytes-dev/everything-claude-marketing --skill editorial-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/skills/brainbytes-dev/everything-claude-marketing/editorial-calendar)<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/editorial-calendar"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/editorial-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/brainbytes-dev/everything-claude-marketing/editorial-calendar"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/editorial-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.00023 | $0.02488 |
| Opus 5.5 | $0.00009 | $0.00995 |
| Sonnet 5.5 | $0.00005 | $0.00498 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade A, and why
editorial-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 2mo 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Calendar
When to Activate
- Starting a content program and need to plan content production
- Content creation feels ad hoc, reactive, or inconsistent
- Scaling content output with multiple contributors or channels
- Aligning content with product launches, campaigns, or seasonal events
- Stakeholders need visibility into what content is planned and when
- Content team is missing deadlines or publishing inconsistently
First Questions
- What channels do you publish to, and at what cadence for each?
- How many content pieces can your team realistically produce per week/month?
- What is the typical lead time from content idea to published piece?
- Who is involved in the content workflow? (Writers, designers, reviewers, approvers?)
- Are there fixed dates you must plan around? (Product launches, events, seasons?)
- What tools does the team currently use for planning and collaboration?
- Do you plan weekly, monthly, or quarterly?
Calendar Structure
Three Planning Horizons
Quarterly view (strategic). High-level themes, campaigns, and pillar distribution. Set once per quarter, reviewed monthly.
Q2 2026:
- Theme: "Scaling Your First Team"
- Campaign: Product launch (May 15)
- Pillar distribution: Productivity (35%), Frameworks (30%), Remote Work (25%), Product (10%)
- Tentpole content: Annual industry report (June)
- Events: Conference X (April 22-24), Webinar series (May)
Monthly view (tactical). Specific content titles, formats, owners, and deadlines. Set two to four weeks before the month begins.
March 2026:
Week 1: Blog post "5 Sprint Planning Mistakes" (Sarah, publish 3/3)
Week 1: Newsletter #22 (Mike, send 3/5)
Week 2: Case study - Acme Corp (Sarah, publish 3/10)
Week 2: LinkedIn carousel - Sprint Planning Tips (Jess, publish 3/11)
...
Weekly view (execution). Day-by-day publishing schedule with status tracking. Updated daily during standups.
Monday 3/3:
09:00 - Blog post goes live (Sarah confirms)
10:00 - Social promotion thread (Jess schedules)
14:00 - Email to subscribers (Mike sends)
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.
- 2mo ago First seen · 274 lines · 23 tokens per session scan A e056574af424
editorial-calendar is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 2,488 once invoked, about $0.0001 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-09-03.
editorial-calendar compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| editorial-calendarbrainbytes-dev/everything-claude-marketing | Skill | 10 | 7mo ago | MIT | A | 23 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |