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 lisbeth718/pseo-skills --skill seo-content-refreshgit clone --depth 1 https://github.com/lisbeth718/pseo-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/lisbeth718/pseo-skills/seo-content-refresh)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/seo-content-refresh"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-content-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/lisbeth718/pseo-skills/seo-content-refresh"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-content-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.00078 | $0.03558 |
| Opus 5.5 | $0.00031 | $0.01423 |
| Sonnet 5.5 | $0.00016 | $0.00712 |
| Haiku 4.5 | $0.00008 | $0.00356 |
Grade A, and why
seo-content-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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Content Refresh and Pruning
Classify every indexed page by its performance trend, then pick one action per class. Decide from data, not from page age.
Inputs
-
GSC export, two periods: two
pull.tsruns fromgsc, one per period, each with full page coverage. Use last 90d vs previous 90d, or last 90d vs the same 90d a year ago when seasonality matters. GSC keeps 16 months of data, so pull and archive monthly.npx tsx <skill-dir>/scripts/pull.ts --site sc-domain:example.com --start 2026-07-01 --end 2026-09-28 --pages 25000 --out data/gsc-current.json npx tsx <skill-dir>/scripts/pull.ts --site sc-domain:example.com --start 2026-04-02 --end 2026-06-30 --pages 25000 --out data/gsc-previous.jsonCannibalization needs query+page rows: add
--dims query,pageto a run and read thequeryPagesarray. -
Page inventory: URL, template/segment, publish date, real last content change (from git or CMS, not the sitemap), canonical, indexability.
-
Optional analytics: conversions or engagement per URL. A page with few clicks but real conversions is not prunable.
Classes
| Class | Definition (heuristics, tune per site) |
|---|---|
| growing | clicks up more than 20% vs prior period, min 30 clicks in either |
| stable | clicks within -20% to +20% |
| decaying | clicks down more than 30% and at least 30 clicks lost, or impressions down more than 40% |
| never-performed | indexable, older than 6 months, under 10 impressions in the whole window |
| cannibalizing | 2+ URLs each get at least 10 impressions for the same query and no URL holds a clear lead (heuristic: top URL under 70% of the query's impressions) |
| low-volume | under 30 clicks in both periods: too noisy to classify, leave alone |
| lost (check indexing) | had at least 30 clicks in the previous period and is missing from the current export (no impressions at all) |
All numbers above are heuristics, not Google rules. Scale them to site size: a site with 500 clicks a month needs lower floors than one with 500k.
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.
- 6d ago First seen · 184 lines · 78 tokens per session scan A 5f3fe90c900c
seo-content-refresh is a skill published in the GitHub repository lisbeth718/pseo-skills (54 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 3,558 once invoked, about $0.0003 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.