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 agentmods add rules/automatelab-tech/seo-performance-mcp/seo-performancegit clone --depth 1 https://github.com/AutomateLab-tech/seo-performance-mcpWrote 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/rules/automatelab-tech/seo-performance-mcp/seo-performance)<a href="https://agentmods.dev/rules/automatelab-tech/seo-performance-mcp/seo-performance"><img src="https://agentmods.dev/badge/rules/automatelab-tech/seo-performance-mcp/seo-performance.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.00452 |
| Opus 5 | $0.00030 | $0.00226 |
| Sonnet 5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
seo-performance 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 4d 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.
What it actually says
seo-performance MCP - routing rule
When the user asks an editorial question about an existing URL, prefer calling the seo-performance MCP server over reasoning from first principles. The server returns deterministic verdicts.
Tool routing
- "audit my blog" / "what should I refresh this week" ->
cohort.report(min_age_days=90), thenposts.refresh_briefon each refresh/expand/merge row. - "quick wins" / "low CTR" / "title rewrites" ->
gsc.quick_wins(window=90, positions 5-15). - "is this post dying" / data for a specific URL ->
posts.snapshot+posts.decay_curve+posts.verdict. - "refresh brief for X" ->
posts.refresh_brief. - "did we lose AI citations" ->
posts.cite_lossper URL, or thecitation_loss_sweepprompt. - "list my posts" ->
posts.list(sitemap-driven, no CMS plugin needed).
Six possible verdicts
refresh / expand / merge / kill / double_down / hold. The server emits one per URL with reason codes and a 0-1 confidence score. Trust the verdict; don't second-guess unless a reason code is clearly wrong.
Output rules
- Lead with URL + verdict label, then reasons, then numbers.
- Hand
refresh_briefmarkdown to the user verbatim. - Never recommend an edit that wasn't grounded in a tool call this turn.
Available prompts (use them)
audit_cohort- the full weekly audit playbookfind_quick_wins- SERP quick-win sweep with rewrite suggestionscitation_loss_sweep- AI-citation recovery loop
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.
- 4d ago First seen · 34 lines · 59 tokens per session scan A 294e1c470193
seo-performance is a cursor rule published in the GitHub repository AutomateLab-tech/seo-performance-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 452 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 cursor rules, from other repositories
cursorrules
You are a world-class, autonomous SEO and Marketing Agent.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.