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 content-arc-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/content-arc-planner)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/content-arc-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/content-arc-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/content-arc-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/content-arc-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.02351 |
| Opus 5 | $0.00024 | $0.01175 |
| Sonnet 5 | $0.00010 | $0.00470 |
| Haiku 4.5 | $0.00005 | $0.00235 |
Grade A, and why
content-arc-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 8d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Arc Planner
What This Skill Does
Plans a multi-edition content arc for a newsletter — mapping themes, topics, and recurring formats across a defined publishing period to give the publication editorial coherence and reader momentum rather than a disconnected series of standalone editions.
When To Use This Skill
- You are planning a new series within your newsletter (e.g. a six-week investigation into a specific topic)
- You are planning a quarter or half-year of editions and need a thematic structure, not just a list of topics
- Your newsletter has become episodic and disconnected, and you want to introduce narrative momentum that builds from edition to edition
- You are launching a new newsletter and want to plan the first eight to twelve editions to establish the publication's range and character
- You want to develop a signature annual arc (e.g. a retrospective issue every December, a seasonal focus in Q1) to give long-term readers something to look forward to
What You Need To Provide
Required: Newsletter name, subject area, and publishing cadence; the time period to plan (e.g. "next 8 editions", "Q2", "12 weeks"); any known fixed events, deadlines, or seasonal hooks that should anchor specific editions Optional: The newsletter's current recurring formats or sections; any topics you have been saving for the right moment; reader feedback themes you want to address; whether you want to introduce any new recurring sections during this arc; your editorial ambition (is this period a good time to go deeper on one subject, or range more widely?)
How the Assistant Approaches This
- Identifies the natural narrative or thematic logic of the period — what questions can this series of editions build toward answering? What would make a reader who reads every edition feel they have gone on a journey rather than just received regular updates?
- Maps an arc structure: an opening edition that establishes the period's central focus, a development phase where individual editions add complexity or explore adjacent angles, and a closing edition that synthesises or resolves the arc without being artificially tidy
- Assigns recurring formats and special formats across the arc — ensuring a mix of depth and accessibility, and flagging which editions could serve as good entry points for new subscribers (important for promotion strategy)
- Flags edition-level hooks, angles, or tensions that will give each entry its own distinct value — an arc should not make individual editions feel like installments that require the others; each one should be independently readable while rewarding the full sequence
- Notes practical production requirements: which editions will need advance research, interviews, or data gathering, so the editor can plan workload accordingly
What ships with it
1 file 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.
- 8d ago First seen · 143 lines · 48 tokens per session scan A 481c3b87e0a1
content-arc-planner is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 2,351 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-04.
Other skills, from other repositories
xiaoyuzhou-podcast-notes
A workflow that turns a public Xiaoyuzhou FM podcast episode into structured Markdown notes and a saved transcript. Xiaoyuzhou FM is a Chinese podcast platform.
c-research
Summarize web URLs, PDFs, YouTube videos, and podcasts using the summarize CLI. Instantly extract key points from any content type without manual reading. Useful for research, link digests, and media review.
Newsletter Summary Writer
Condenses long articles, threads, or documents into concise, engaging newsletter-ready summaries.
transcript-ingestion
Transcript ingestion authority — capture, normalize, and prioritize transcripts from YouTube videos, podcast pages, captions, show notes, and transcript-like page content for persona systems, RAG pipelines, and grounded synthesis.
breakout-strategy-engine
Pre-built breakout strategy templates — volatility squeeze detection, range breakout, momentum breakout with confirmation filters. Use this skill whenever the user asks about "breakout strategy", "Bollinger squeeze", "range breakout", "momentum breakout", "volatility expansion", "ATR breakout", "Donchian breakout"…
competitive-analyzer
Structured competitive teardown for product discovery - surface the 4-6 dimensions buyers actually weigh, score every competitor on each, and identify exploitable gaps. Use when: competitive analysis, competitor teardown, market positioning, where do we win, where do we lose, competitive gap analysis, competitor audit.