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 event4u-app/agent-config --skill editorial-calendargit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/editorial-calendar)<a href="https://agentmods.dev/skills/event4u-app/agent-config/editorial-calendar"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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/event4u-app/agent-config/editorial-calendar"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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.00042 | $0.01959 |
| Opus 5 | $0.00021 | $0.00979 |
| Sonnet 5 | $0.00008 | $0.00392 |
| Haiku 4.5 | $0.00004 | $0.00196 |
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 7d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
editorial-calendar
When to use
- A content programme is producing assets in bursts (campaign-shaped only) and the cadence is brittle the quarter the campaign rests.
- The team owes more drafts than it can ship and the backlog is functioning as content-debt rather than queue — surface and prioritise.
- A new audience-by-message matrix exists and the team needs to translate it into a repeating cadence with beat-mapping across channel stages.
Do NOT use to draft the asset itself (downstream), pick channel-
specific tactics like ad creative or email subject lines (out of
scope — channel-agnostic skill), or sequence a one-off launch wave
(route to gtm-launch).
Cognition cluster
- Mental model 3 — Pareto principle (80/20). Roughly 20 % of
the editorial beats produce 80 % of the audience pull. The
calendar is the discipline of doubling down on the 20 % and
letting the 80 % be reactive, not core. See
docs/contracts/mental-models.md§ 3. - Mental model 18 — Pull vs. push systems. Evergreen content is
a pull system (the audience finds it); campaigns are a push
system (we time the arrival). The calendar separates the two so
campaign collapse does not collapse pull. See
mental-models.md§ 18. - Context-spine — product + customer-segment + channel-stage +
funnel-stage. Read product for what is shippable as proof,
customer-segment for who reads which beat, channel-stage
for where the audience is in the awareness arc, and
funnel-stage for whether a beat is top-of-funnel reach or
mid-funnel proof. See
context-spine.
Procedure
Step 0: Inherit the message stack and audience matrix
Identify the locked primary-message.md, supporting-proofs.md,
and audience-matrix.md from
messaging-architecture. The
editorial calendar is a cadence translation of the matrix; without
the matrix it is content-as-impulse, not content-as-system.
What ships with it
2 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.
- 7d ago First seen · 173 lines · 42 tokens per session scan A 1d036112fb0c
editorial-calendar is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,959 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-09-03.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.