What is recovery-full?

A command that combines diagnosis, crawling, auditing, planning, and monitoring into one recovery workflow. It is designed for recovering or checking websites while controlling when changes may be made.

It is for running a complete website recovery process from initial diagnosis through monitoring, while keeping read-only checks separate from approved live changes.

It gives the recovery process one tracked run and applies safeguards before live edits, including a change plan, quality checks, history records, and settlement-gate restrictions.

recovery-full — 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-full/github.svg)](https://agentmods.dev/commands/maxschottke-spec/seo-survival-kit/recovery-full)

Your own site

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

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

When invoked 3,133 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.00020	$0.03133
Opus 5	$0.00010	$0.01566
Sonnet 5	$0.00004	$0.00627
Haiku 4.5	$0.00002	$0.00313

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

Security

Grade A, and why

recovery-full 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-full.md · 271 lines

How it starts

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

Recovery Full Workflow

Zweck

Verkettung aller fuenf Recovery-Commands in einem Durchlauf (Diagnose -> Crawl -> Audit -> Plan -> Monitor). Ein Befehl fuer den vollstaendigen Recovery-Workflow von Diagnose bis Monitoring-Setup. Alle Schritte teilen eine gemeinsame run_id fuer end-to-end Traceability.

Change Governance

Keine Live-Aenderungen ohne expliziten Modus + Budget + Freigabe. Bei breiten Instruktionen wie "alles", "mach alles", "ALLESS": Hard Stop per SEO_CHANGE_GOVERNOR.md.

Vor jedem Write: Change Plan ausgeben. Nach jedem Write: Live QA + change-history.ndjson Eintrag. Budget-Tracking ueber die gesamte Session. recovery-audit muss VOR der ersten Schreiboperation laufen wenn change-history.ndjson existiert.

Settlement-Gate-Verhalten (Pflicht)

Wenn ~/.cache/seo-rescue/{slug}/recovery-gate.json mit settlement_gate_active: true existiert:

recovery-full darf keine Live-Aenderungen vorschlagen oder durchfuehren
recovery-full darf nur folgende Schritte ausfuehren:
- Diagnose (read-only)
- Crawl (read-only)
- Audit (read-only)
- Monitoring-Render (read-only)
- Re-Evaluation-Report
- Ticketliste fuer Rico / Entwicklung
- Plan-After-Gate-Dokument anstelle eines normalen Action-Plans

Wenn der User trotzdem Live-Aenderungen fordert

Stop mit Begruendung
Keine Ausfuehrung
Konkrete Unlock-Kriterien aus SEO_SETTLEMENT_GATE.md section 9 nennen
Standard Settlement-Gate Response aus SAFE_LIVE_CHANGE_RULES.md ausgeben
Hinweis auf next_allowed_review_date aus dem Gate-Objekt

Plan-After-Gate-Dokument

Statt eines normalen Action-Plans erzeugt recovery-full bei aktivem Gate ein Plan-After-Gate-Dokument:

{
  "type": "plan_after_gate",
  "settlement_gate_active": true,
  "live_changes_allowed": false,
  "next_allowed_review_date": "...",
  "prepared_now": [
    "schema_drafts",
    "title_drafts",
    "rico_briefings",
    "rollback_plans"
  ],
  "deferred_until_unlock": [
    "title_rewrites",
    "internal_link_additions",
    "cms_slot_patches",
    "category_deactivations"
  ],
  "unlock_criteria_status": {
    "time": "not_met|met",
    "data": "not_met|partial|met",
    "stability": "not_met|partial|met",
    "decision": "not_met|met"
  }
}

Read the full file on GitHub · 271 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 · 271 lines · 20 tokens per session scan A 34fb55f3b094

Subscribe to this mod's changes

recovery-full is a command published in the GitHub repository maxschottke-spec/seo-survival-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 3,133 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.

Claude Code Debugging claude-code-plugin dataforseo pdf-report rescue

recovery-full

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 Full Workflow

Zweck

Change Governance

Settlement-Gate-Verhalten (Pflicht)

Wenn der User trotzdem Live-Aenderungen fordert

Plan-After-Gate-Dokument

What this file has done since we first saw it

Other commands, from other repositories

linkerd

debug

ia-report-bug

data-flow-analysis

duck-off

bug