Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add maxschottke-spec/seo-survival-kit/plugin install seo-rescueWrote 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/sistrix-monday-recovery-check)<a href="https://agentmods.dev/skills/maxschottke-spec/seo-survival-kit/sistrix-monday-recovery-check"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/sistrix-monday-recovery-check/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/sistrix-monday-recovery-check"><img src="https://agentmods.dev/badge/skills/maxschottke-spec/seo-survival-kit/sistrix-monday-recovery-check.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.00235 | $0.04487 |
| Opus 5 | $0.00118 | $0.02243 |
| Sonnet 5 | $0.00047 | $0.00897 |
| Haiku 4.5 | $0.00023 | $0.00449 |
Grade A, and why
sistrix-monday-recovery-check 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SISTRIX Monday Recovery Check
Overview
During an active SEO recovery, every Monday the operator asks the same questions: did rankings recover, are money keywords holding, are winners and losers offsetting each other, is the visibility index lagging behind actual ranking gains. Without structure, the answer is ad-hoc and biased toward whatever the operator opens first in the SISTRIX UI.
This skill turns the Monday review into a fixed 17-section report so the same questions get answered consistently week over week. The full methodology lives in ${CLAUDE_PLUGIN_ROOT}/references/SISTRIX_MONDAY_RECOVERY_CHECK.md (canonical spec) and ${CLAUDE_PLUGIN_ROOT}/references/RECOVERY_SYSTEM.md (operational detail for sections 4-10). All later SISTRIX_MONDAY_RECOVERY_CHECK.md §N / RECOVERY_SYSTEM.md §N / DECISION_ENGINE.md mentions in this file refer to those files under ${CLAUDE_PLUGIN_ROOT}/references/. This SKILL.md is the runnable skill that executes that workflow against the operator's CSV exports.
When to use
- A domain in an active recovery from a Google Core Update or AI Overview reshuffle and the operator wants a weekly structured pulse
- A new SISTRIX export landed and the operator wants to know "is the recovery working" without manually eyeballing 12 charts
- The operator suspects winner/loser neutralization is masking actual recovery and wants the numbers
- The operator is about to make a content or template change to a winning URL and wants a "what not to touch" check first
- An agency client deliverable: a consistent Monday report format the client can read in 5 minutes
Don't use for:
- Brand-new recovery diagnosis (use [[post-core-update-recovery]] for the initial diagnostic)
- A one-off audit (use [[seo-outreach-report]] for the full decision-maker PDF instead)
- Pre-recovery baselining (run [[psi-weekly-cron-baseline]] alongside instead — that is the technical-health pulse, this skill is the ranking pulse)
- Decisions about specific URL templates or code (this skill produces direction; the operator's team handles execution)
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 · 279 lines · 235 tokens per session scan A a925c72ee6cc
sistrix-monday-recovery-check is a skill published in the GitHub repository maxschottke-spec/seo-survival-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 235 tokens to every session and 4,487 once invoked, about $0.0012 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.
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.
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.
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…
start
Friendly first-run alias that routes new Agentic SEO users to the canonical agentic-seo and project-init workflow without duplicating process rules.
autoresearch
When the user wants a rigorous iteration loop for an artifact, prompt, briefing, content structure, or Agentic SEO skill. Also use for Karpathy-style experiment runs that need baseline scoring, explicit metrics, stop rules, and keep/reject decisions.