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 traffic-decay-detectorgit 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/traffic-decay-detector)<a href="https://agentmods.dev/skills/marketingskills/seo/traffic-decay-detector"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/traffic-decay-detector/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/traffic-decay-detector"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/traffic-decay-detector.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.00056 | $0.00645 |
| Opus 5 | $0.00028 | $0.00322 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
traffic-decay-detector 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traffic Decay Detector
Overview
Identify pages with declining organic traffic, what queries are driving the loss, and which pages are worth refreshing. Works with live GSC/GA4 data (via marketingskills/seo/skills/live-search-console-data) or pasted exports.
Inputs
- Current period GSC data (queries + pages): clicks, impressions, CTR, avg position
- Prior period GSC data (same dimensions, same property)
- Optional: GA4 landing page sessions or conversion data
- Optional: threshold for minimum clicks (default: 10 clicks/period)
If no live data is available, ask the user to paste GSC exports for both periods.
Workflow
- Load GSC data from live connection or pasted export.
- Compare current period vs prior period for each page.
- Calculate absolute and relative change for clicks, impressions, CTR, position.
- Filter to pages with click decline > configured threshold.
- For each declining page, find which queries drove the loss.
- Classify the cause: SERP position drop, CTR collapse, impression loss, or seasonal.
- Surface the queries with the biggest click loss per page.
- Rank pages by total click loss and confidence in recovery.
- Recommend refresh candidates with rationale.
Output Format
## Traffic Decay Report
**Period:** [current range] vs [prior range]
**Pages analyzed:** N
**Declining pages found:** N
### Top Declining Pages
| Page | Clicks (curr) | Clicks (prev) | Change | Primary Query | Cause |
|---|---|---|---|---|---|
| /page-url | 1,200 | 2,000 | -800 (-40%) | "keyword" | Position drop (2→6) |
### Top Queries Driving Decline
| Query | Click Loss | Current Pos | Prior Pos | Page Affected |
|---|---|---|---|---|
### Refresh Candidates
Priority-ordered list with reasoning.
### Stable Pages (for reference)
Pages with flat or growing traffic.
Interpretation
- A page losing clicks while impressions are stable likely has a CTR or ranking issue.
- A page losing both clicks and impressions may have lost search volume or been overtaken.
- Pages with high impression counts and low CTR may need title/meta rewrites or featured snippet targeting.
- Seasonal declines should be marked but not recommended for immediate refresh unless the trend is accelerating.
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 · 70 lines · 56 tokens per session scan A 15d95077b5dc
traffic-decay-detector is a skill published in the GitHub repository marketingskills/seo (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 645 once invoked, about $0.0003 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-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-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-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…
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…