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 marketingskills/seo --skill content-refresh-briefgit clone --depth 1 https://github.com/marketingskills/seoWrote 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/marketingskills/seo/content-refresh-brief)<a href="https://agentmods.dev/skills/marketingskills/seo/content-refresh-brief"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/content-refresh-brief/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/marketingskills/seo/content-refresh-brief"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/content-refresh-brief.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.00044 | $0.00600 |
| Opus 5 | $0.00022 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
content-refresh-brief 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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Refresh Brief
Overview
Given a URL and optionally its GSC/GA4 performance data, produce a structured refresh brief that covers SERP intent analysis, entity gaps, content outline, internal link plan, and technical recommendations.
Inputs
- URL of the page to refresh
- Current GSC performance (clicks, impressions, CTR, avg position, top queries)
- Prior period GSC performance for comparison
- Optional: page content (if the user pastes it)
- Optional: GA4 engagement or conversion data
Workflow
- Search the page's primary query in a current SERP.
- Analyze top 5 organic results for:
- Content format (guide, list, tool, video, etc.)
- Content depth (word count, section count, entities covered)
- Date freshness (when each page was last updated)
- SERP features present (featured snippets, People Also Ask, video, etc.)
- Compare current page content against SERP expectations:
- Does it match the dominant content format?
- Are key entities missing?
- Is the content depth competitive?
- Is the page fresh enough?
- Review GSC query data to identify:
- Queries with declining CTR despite stable impressions
- Queries where the page ranks but doesn't satisfy intent
- Queries from the prior period that stopped driving traffic
- Recommend:
- Content changes (restructure, expand, add sections, update data)
- Technical changes (title, meta description, schema, canonical)
- Internal link additions (from high-traffic pages)
- Entities to add or strengthen
- Estimate effort and expected recovery.
Output Format
## Refresh Brief: /page-url
### Current Performance
| Metric | Current | Prior | Change |
|---|---|---|---|
### SERP Intent Analysis
[Format, depth, freshness expectations from top results]
### Gap Analysis
| Gap | Competitor Example | Our Action |
|---|---|---|
### Recommended Content Changes
1. [Action with details]
### Recommended Technical Changes
1. [Action with details]
### Internal Link Plan
| Source Page | Anchor Text | Rationale |
|---|---|---|
### Effort Estimate
[Low / Medium / High] — [estimated hours]
### Expected Recovery
[Estimated click/impression recovery range]
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.
- 10d ago First seen · 82 lines · 44 tokens per session scan A 38b5778fa048
content-refresh-brief is a skill published in the GitHub repository marketingskills/seo (3 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 600 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-08-31.
Other skills, from other repositories
os-check-work
ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against…
os-done-or-not
ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from…
os-step-by-step
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do"…
os-what-could-go-wrong
ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision…
os-ask-simple
ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - or ask if something is worth doing or if something simpler would do, in any language. Rewrites the question in plain…
os-whats-next
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is…