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 refreshgit 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/refresh)<a href="https://agentmods.dev/skills/rightblogger/bloggingskills/refresh"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/refresh/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/refresh"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/refresh.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.00147 | $0.01352 |
| Opus 5.5 | $0.00059 | $0.00541 |
| Sonnet 5.5 | $0.00029 | $0.00270 |
| Haiku 4.5 | $0.00015 | $0.00135 |
Grade A, and why
refresh 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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh
You bring a published post back up to date so it earns its traffic and its citations again. Most decaying posts don't need a rewrite. They need the right fix for the reason they slipped, which is why you diagnose before you edit.
You're done when you've named the cause of the decline, every fact, number, link, and version in the post is current or flagged, the post covers what readers now expect, and nothing the post still ranks for was removed.
Initial assessment
- Read
.agents/blog-context.mdfor audience, voice, and the "Experience and proof" section, which is where new first-hand detail can come from. - Read the house-style rulebook at
../house-style/references/ai-tells.mdbefore you write anything new. - Get the post: a URL to fetch or the pasted text, plus the publish date if known.
- Gather what data you can reach. With Search Console connected, pull this page's clicks, impressions, average position, and top queries for the last three months against the same period a year earlier. With a SERP or web tool, read the current top results for the post's main query. With neither, work from the post itself and say the diagnosis is inferred.
Method
1. Diagnose the decline
Match the evidence to a cause. Each one calls for a different fix.
| Cause | What you see | Fix |
|---|---|---|
| Outdated | Old prices, versions, screenshots, years, dead links | Update facts in place |
| Intent shift | The top results are now a different format (a tool, a list, a video) | Restructure to the format that wins |
| Outpaced | Competitors added depth, original data, or better examples | Add the missing coverage and real information gain |
| Cannibalized | Another page on the same site ranks for the same queries | Merge into one page and redirect the other |
| Absorbed by AI answers | Impressions steady or rising, clicks falling, position stable | Make it the cited source (ai-seo) and give readers a reason to click |
| Discover-only drop | Search clicks steady, Discover traffic gone | Check the headline for clickbait and the post for depth and timeliness; check the lead image is large and original |
| Not a content problem | Deindexed, a title rewritten in the SERP, a site-wide drop, the site opted out of AI features in Search Console | Report it; editing the post won't help |
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.
- 5d ago Changed · +3 lines 9d42e9f8779b
- 11d ago First seen · 97 lines · 147 tokens per session scan A 1e6f31c7d6d1
refresh is a skill published in the GitHub repository RightBlogger/bloggingskills (3 stars, last pushed 5d ago), licensed MIT. It adds 147 tokens to every session and 1,352 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…