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 RightBlogger/bloggingskills --skill content-plangit clone --depth 1 https://github.com/RightBlogger/bloggingskillsWrote 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/rightblogger/bloggingskills/content-plan)<a href="https://agentmods.dev/skills/rightblogger/bloggingskills/content-plan"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/content-plan/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/rightblogger/bloggingskills/content-plan"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/content-plan.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.00156 | $0.01040 |
| Opus 5.5 | $0.00062 | $0.00416 |
| Sonnet 5.5 | $0.00031 | $0.00208 |
| Haiku 4.5 | $0.00016 | $0.00104 |
Grade A, and why
content-plan 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 11d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content plan
You decide what this blog should publish next. The output is a short, ranked list of posts where each one targets a distinct search intent, ladders up to a pillar, and has an angle the blog can actually back with experience or data.
You're done when every planned post has a distinct intent no existing page already serves, a pillar, a page type, and a reason it should exist, and the list is ordered by what to write first.
Initial assessment
- Read
.agents/blog-context.md. The pillars, audience, goal, and "Experience and proof" sections drive this plan. If it doesn't exist, run blog-context first or infer the pillars from the site and label them as inferred. - Get the inventory of what's already published: a sitemap, a CMS export, or a pasted list of URLs and titles. Without one, plan anyway but say you couldn't check for duplicates.
- Use data when it's connected. Search Console shows queries the site already gets impressions for, which is the strongest source of ideas. A keyword or SERP tool adds demand and difficulty. With neither, estimate and label estimates as such.
- Default to 10 to 15 new posts unless the user asks for a number.
Method
- Map the inventory. Sort existing posts under the pillars and note which pillars are thin. Pages that target the same intent as each other are cannibalization; list them for a merge.
- Gather candidates for each pillar from:
- Search Console queries with impressions but no page built for them. (Existing pages stuck on positions 8 to 20 belong on the refresh list instead.)
- The real problems and questions in the audience section (keyword-research can expand any one of them).
- Comparisons, alternatives, and "how to choose" decisions readers face.
- The Experience and proof section. Posts built on the author's own tests, data, or stories are the ones competitors can't copy, and they're what readers, search engines, and AI answers reward.
- One page per intent. Merge candidates that a single page would satisfy. A quick test: if the same results rank for both searches, it's one post. Drop any candidate an existing page already serves, and add that page to the refresh list if it serves it badly.
- Score each survivor on four things: fit with the blog's goal, reader demand, winnability (forums, thin pages, or outdated posts in the top results mean an opening), and the unique angle this blog can bring. Cut anything that scores low on the last one; a post with no angle is filler. Spread the proof: if three candidates all lean on the same test or story, keep the strongest one and fold the rest in, or the posts will repeat each other.
- Shape clusters. For each pillar, name the hub page (existing or planned) and make sure supporting posts link up to it and across to siblings.
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.
- 11d ago First seen · 80 lines · 156 tokens per session scan A 66253b1aca78
content-plan is a skill published in the GitHub repository RightBlogger/bloggingskills (3 stars, last pushed 5d ago), licensed MIT. It adds 156 tokens to every session and 1,040 once invoked, about $0.0006 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-10-12.
Other skills, from other repositories
affiliate-blog-builder
Write SEO-optimized affiliate blog articles, product reviews, comparison posts, listicles, and how-to guides. Triggers on: "write a blog post about", "review of [product]", "best [category] article", "comparison blog", "affiliate blog", "SEO article", "write a review", "product roundup", "blog content for affiliate"…
comparison-post-writer
Write "X vs Y" comparison blog posts that help readers choose between two competing products. Triggers on: "write a comparison post", "X vs Y blog post", "compare [product A] and [product B]", "which is better [A] or [B]", "head to head comparison", "[product] vs [product] article", "comparison review", "write a…
how-to-tutorial-writer
Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for…
listicle-generator
Write "Top N best..." listicle articles for affiliate marketing with mini-reviews, pricing, pros/cons, and CTAs per entry. Triggers on: "write a best of list", "top 10 [category] tools", "best [product category] article", "roundup post", "listicle about [category]", "write a top tools article", "best [N] alternatives…
content-moat-calculator
Estimate pages needed for topical authority. Go/no-go decision before investing months in content. Triggers on: "how much content do I need", "topical authority estimate", "content moat", "how many articles", "content gap analysis", "can I compete in this niche", "content investment calculator", "is this niche worth…
keyword-cluster-architect
Map 50-200+ keywords into topical clusters for SEO domination. Build content roadmaps for topical authority. Triggers on: "keyword research", "keyword clustering", "topical authority", "keyword map", "keyword strategy", "content roadmap for SEO", "keyword grouping", "topic clusters", "SEO keyword plan", "map my…