What is recovery-diagnose?

A read-only SEO diagnosis command for investigating why a website domain has lost search visibility. It checks possible core-update effects, visibility changes, lost keywords, and the backlink profile.

Use it to audit a domain after search-performance declines, quantify visibility drops, identify lost keywords, review backlinks, and produce evidence for later recovery decisions.

It creates a structured report for recovery work without changing the live shop. It also records sources and confidence for findings and reports whether a separate settlement gate is active.

recovery-diagnose — Command for Claude Code by maxschottke-spec

Install

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.

Clone the repo

git clone --depth 1 https://github.com/maxschottke-spec/seo-survival-kit

Made for: Claude Code.

Or install seo-rescue, the plugin that ships this one along with the rest of its 18 skills, 6 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose/github.svg)](https://agentmods.dev/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose)

Your own site

<a href="https://agentmods.dev/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose"><img src="https://agentmods.dev/badge/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose"><img src="https://agentmods.dev/badge/commands/maxschottke-spec/seo-survival-kit/recovery-diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 10,488 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.10488
Opus 5	$0.00009	$0.05244
Sonnet 5	$0.00003	$0.02098
Haiku 4.5	$0.00002	$0.01049

Measured 12d ago against content hash ffc8d4676c58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

recovery-diagnose 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 12d 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.

plugins/seo-rescue/commands/recovery-diagnose.md · 661 lines

How it starts

The opening of the file, as written. The whole thing — 661 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Recovery Diagnose

Zweck

Automatische Diagnose einer Domain: Core-Update-Betroffenheit pruefen, VI-Drop quantifizieren, Keyword-Verluste identifizieren, Backlink-Profil scannen. Ergebnis ist ein strukturierter Befund als Grundlage fuer alle weiteren Recovery-Commands.

Change Governance

Mode: audit_only. Change Budget: 0. Keine Live-Shop-Writes. Nur Cache-Report-Artefakte.

Wenn change-history.ndjson existiert, wird sie am Anfang gelesen und im Befund referenziert. Jede Aussage muss Quelle und Confidence tragen.

Settlement Gate Awareness

Dieses Command ist read-only (audit_only, Change Budget 0) — ein aktiver Settlement Gate (../../references/SEO_SETTLEMENT_GATE.md) blockiert es NIE. Es muss den Gate-State aber kennen und ausweisen:

Lies ~/.cache/seo-rescue/{slug}/recovery-gate.json, falls vorhanden. Writer dieser Datei ist recovery-audit (siehe commands/recovery-audit.md, Schritt 7: Settlement-Gate-Detection) — recovery-diagnose liest sie nur. Fehlt die Datei, gilt der Gate als never_triggered: keine Warnung, normaler Ablauf.
Falls settlement_gate_active = true:
- Diagnose laeuft normal weiter — read-only Analyse ist waehrend eines aktiven Gates immer erlaubt.
- In den Befund (Top-Level) das Feld settlement_gate_status aufnehmen, gespiegelt aus der Gate-Datei:
```
"settlement_gate_status": {
  "active": true,
  "next_allowed_review_date": "2026-06-06",
  "unlock_status": "blocked"
}
```
  (unlock_status: blocked | partial | open, direkt aus der Gate-Datei uebernommen.)
- In der User-Ausgabe eine Zeile ausgeben: Settlement Gate: AKTIV bis {next_allowed_review_date} — read-only Diagnose erlaubt, Live-Aenderungen blockiert
- Jeder Empfehlungstext (insbesondere summary_de und der "Naechster Schritt") darf KEINE sofortigen Live-Aenderungen vorschlagen. Naechste Schritte als "jetzt vorbereiten/Drafts erstellen, Ausfuehrung nach Gate-Re-Evaluation" formulieren (prepare_now_execute_later-Prinzip aus SEO_SETTLEMENT_GATE.md).
Falls Gate-Datei fehlt oder settlement_gate_active = false: settlement_gate_status: { "active": false } in den Befund schreiben. Keine User-Ausgabe-Zeile noetig.

Read the full file on GitHub · 661 lines

Changes

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.

12d ago First seen · 661 lines · 17 tokens per session scan A ffc8d4676c58

Subscribe to this mod's changes

recovery-diagnose is a command published in the GitHub repository maxschottke-spec/seo-survival-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 10,488 once invoked, about $0.0001 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.

Analytics and metrics Claude Code Marketing and SEO claude-code-plugin dataforseo pdf-report rescue

recovery-diagnose

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Recovery Diagnose

Zweck

Change Governance

Settlement Gate Awareness

What this file has done since we first saw it

Other commands, from other repositories

seo-content

spec-driven

prototype

init

brand-generate

genshijin-compress