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 ur-grue/autopunk-media-skills --skill editorial-calendar-plannergit clone --depth 1 https://github.com/ur-grue/autopunk-media-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/ur-grue/autopunk-media-skills/editorial-calendar-planner)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner/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/ur-grue/autopunk-media-skills/editorial-calendar-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 456 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00038 | $0.10642 |
| Opus 5.5 | $0.00015 | $0.04257 |
| Sonnet 5.5 | $0.00008 | $0.02128 |
| Haiku 4.5 | $0.00004 | $0.01064 |
Grade A, and why
editorial-calendar-planner 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Calendar Planner
What This Skill Does
Generates a structured editorial calendar for a publication — mapping content across weeks or months, balancing evergreen and timely pieces, tracking production stages, and aligning coverage with external events.
When To Use This Skill
- You are planning the next quarter's coverage and need a skeleton calendar before assigning stories
- Your publication has a seasonal peak (awards season, festival coverage, holiday gift guides) and you need to reverse-engineer the production timeline from the publish dates
- You have recently expanded or shrunk your team and need to redistribute workload across writers
- An editor-in-chief is onboarding and wants to see the full pipeline visualised in one document
- You are launching a new publication or section and need to build the first production schedule from scratch
- You need to coordinate coverage across multiple beats that share the same production bottleneck (a single photographer, one copy editor, a shared designer)
- You want to stress-test an existing rough plan: you have a list of stories you want to run but have not mapped them against the calendar to check for bottlenecks, workload peaks, or deadline conflicts
- You are preparing a planning document for a stakeholder meeting (editorial board, publisher, funder) and need to show what the team will produce over the next period
What You Need To Provide
Required:
- Publication type and frequency (weekly, biweekly, monthly, daily digital)
- Team size — how many writers, editors, and other production staff
- Beat coverage — which subjects your publication covers
- Planning period — the timespan you want the calendar to cover (4–12 weeks)
Optional:
- Upcoming external events relevant to your beats (festivals, elections, legislative sessions, industry conferences, awareness weeks, holidays)
- Existing recurring content (regular columns, series, reviews sections)
- Any hard editorial commitments already on the schedule (commissioned features, pre-sold advertorial adjacencies, special issues)
- Preferred content mix (e.g., "we want more long-form features and fewer news recaps")
- Historical patterns — which types of content perform best, which weeks are slow for readership
- Production bottleneck information — does photography take longer than writing? Is the copy desk a single person?
- Writer availability notes — part-time schedules, planned leave, other commitments
- Whether you want the calendar to include web/digital slots alongside print, or print only
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 · 503 lines · 38 tokens per session scan A 233c1ed01fa0
editorial-calendar-planner is a skill published in the GitHub repository ur-grue/autopunk-media-skills (40 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 10,642 once invoked, about $0.0002 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-04.
Other skills, from other repositories
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
scenario-team-admin
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and…
punch-list-manager
Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.