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 maxschottke-spec/seo-survival-kit --skill post-core-update-recoverygit clone --depth 1 https://github.com/maxschottke-spec/seo-survival-kitWrote 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/maxschottke-spec/seo-survival-kit/post-core-update-recovery)<a href="https://agentmods.dev/skills/maxschottke-spec/seo-survival-kit/post-core-update-recovery"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/post-core-update-recovery/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/maxschottke-spec/seo-survival-kit/post-core-update-recovery"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/post-core-update-recovery.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.00154 | $0.02711 |
| Opus 5 | $0.00077 | $0.01355 |
| Sonnet 5 | $0.00031 | $0.00542 |
| Haiku 4.5 | $0.00015 | $0.00271 |
Grade A, and why
post-core-update-recovery 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Core-Update Recovery
Overview
A specific recovery framework for domains that lost visibility after a Google Core Update. Core insight from real March/April 2026 recovery cases: Authority items > technical hygiene. Recovery 6–12 months, not 6–8 weeks.
When to use
- VI drop correlates timely with a published Core Update (see Google Search Status Dashboard)
- Drop is broad (many keywords simultaneously, not pinpoint)
- Pages keep indexing normally, no technical break
- GSC shows no manual action
- Pattern: 1–6 weeks of decline, then bottoming out
Don't use for:
- Point keyword losses → usually on-page issue, not core update
- Drop coincides with migration / theme change / robots change → that's technical, not core
- Drop is <20 % from peak → can be normal market noise
Diagnosis decision tree
digraph diag {
"Visibility dropped?" [shape=diamond];
"Correlates with Core Update date?" [shape=diamond];
"Brand keywords also dropped?" [shape=diamond];
"Manual action in GSC?" [shape=diamond];
"CWV suddenly red?" [shape=diamond];
"Apply Recovery (this skill)" [shape=box,style=filled,fillcolor=lightblue];
"Technical problem first" [shape=box,style=filled,fillcolor=lightyellow];
"Penalty workflow, not here" [shape=box,style=filled,fillcolor=lightcoral];
"Performance-first workflow" [shape=box,style=filled,fillcolor=lightyellow];
"Market noise, observe" [shape=box];
"Visibility dropped?" -> "Correlates with Core Update date?" [label="yes"];
"Correlates with Core Update date?" -> "Manual action in GSC?" [label="yes"];
"Manual action in GSC?" -> "Penalty workflow, not here" [label="yes"];
"Manual action in GSC?" -> "Brand keywords also dropped?" [label="no"];
"Brand keywords also dropped?" -> "Technical problem first" [label="yes"];
"Brand keywords also dropped?" -> "CWV suddenly red?" [label="no"];
"CWV suddenly red?" -> "Performance-first workflow" [label="yes"];
"CWV suddenly red?" -> "Apply Recovery (this skill)" [label="no"];
"Correlates with Core Update date?" -> "Market noise, observe" [label="no"];
}
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.
- 11d ago First seen · 179 lines · 154 tokens per session scan A 85f256250df1
post-core-update-recovery is a skill published in the GitHub repository maxschottke-spec/seo-survival-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 154 tokens to every session and 2,711 once invoked, about $0.0008 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
content-seo
When the user wants to brief, write, review, optimize, or publish public SEO content. Also use for article outlines, blog posts, landing-page copy, refreshes, and ranking-oriented editorial drafts.
backlink-analysis
When the user wants backlink, referring-domain, anchor, link-quality, link-gap, link-intersect, anchor-diff, link-velocity, brand-mention, or competitor link-profile analysis for one target domain or URL.
brain-keeper
When the user wants to ingest sources, change brain pages, register decisions, catalog content publications, or lint brain pages for provenance and link integrity.
competitive-analysis
When the user wants to compare domains or URLs against competitors across SEO footprint, share of voice, keyword/content gap, head-to-head pages, off-page link gap (via backlink-analysis), and brand positioning. Orchestrates evidence from serp-extract, keyword-research, backlink-analysis, and topic-cluster without…
internal-links
When the user wants internal link opportunities, contextual link recommendations, anchor text improvements, or validation before applying internal links.
start
Friendly first-run alias that routes new Agentic SEO users to the canonical agentic-seo and project-init workflow without duplicating process rules.