seo-pro-max

seo-pro-max is a cursor rule for Cursor from aycanozarpaci/seo-pro-max-skill. It costs 0 tokens per session (20,586 once invoked), scanned B, original, MIT.

A set of rules for adding search-engine optimisation, or SEO, to an existing project. SEO is the practice of helping search engines understand and display a website, and these rules require the project to be inspected before changes are proposed.

In plain words
What is it for?
Use it to review a project’s framework, rendering, and routing setup, then guide decisions about SEO changes across supported coding environments.
Why use it?
It prevents an agent from silently choosing a framework, file location, database table, or admin-panel location. The user is shown options and must decide before files are changed.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: reads .claude/ paths; mentions Claude Code; built for cline.

Good fit Use it to review a project’s framework, rendering, and routing setup, then guide decisions about SEO changes across supported coding environments.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max
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/aycanozarpaci/seo-pro-max-skill

Made for: Cursor.

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.

agentmods badge for seo-pro-max

README.md
[![agentmods](https://agentmods.dev/badge/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max/github.svg)](https://agentmods.dev/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max)
Your own site
<a href="https://agentmods.dev/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max"><img src="https://agentmods.dev/badge/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max/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.

agentmods 80×15 button for seo-pro-max

Your own site · 80×15
<a href="https://agentmods.dev/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max"><img src="https://agentmods.dev/badge/rules/aycanozarpaci/seo-pro-max-skill/seo-pro-max.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 20,586 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.20586
Opus 5 $0.00000 $0.10293
Sonnet 5 $0.00000 $0.04117
Haiku 4.5 $0.00000 $0.02059

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

Security

Grade B, and why

seo-pro-max scanned grade B with 2 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 9d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| Continue.dev | Reference in `~/.continue/config.json` under `customCommands` / `rules` |

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `curl -I` the homepage and one inner route; show response headers.
platforms/cursor/seo-pro-max.mdc · 1,143 lines

How it starts

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

seo-pro-max

A cross-IDE SEO skill. Works with Claude Code, Cursor, Windsurf, Cline / Roo Code, GitHub Copilot Chat, Continue.dev, Aider, Zed AI, and any agent that can read a Markdown rules file.

Core Principle

This skill does not decide. The user decides; this skill executes.

  • The skill MUST NOT silently pick frameworks, file locations, database tables, or admin-panel placements.
  • The skill MUST present options and wait for the user before writing files.
  • The skill MUST analyze the existing project before suggesting anything.

If the agent is tempted to "just pick the obvious one," it must stop and ask instead.


Operating Protocol (Mandatory Order)

Phase 0 — Read the project

Before any question, the agent must inventory:

  1. Framework / runtime — look for package.json, composer.json, requirements.txt, pyproject.toml, Gemfile, go.mod, pubspec.yaml, next.config.*, nuxt.config.*, astro.config.*, vite.config.*, remix.config.*, svelte.config.*, artisan, manage.py.
  2. Rendering model — SSR / SSG / SPA / hybrid / RSC / ISR.
  3. Routing convention — file-based (app/, pages/, src/routes/, src/pages/) vs. controller-based (Laravel routes/web.php, Django urls.py, Express routers).
  4. Existing SEO surface — any current <head> management, metadata exports, Helmet, next/head, useSeoMeta, blade @section('meta'), etc.
  5. Admin panel — presence of a backoffice (app/(admin), admin/, /dashboard, Filament, Nova, Django admin, Strapi, custom).
  6. Database — ORM (Prisma, Drizzle, Sequelize, TypeORM, Eloquent, Django ORM), migrations folder, existing settings/options table.
  7. i18n — next-intl, next-i18next, vue-i18n, nuxt-i18n, Laravel locales, Django i18n.
  8. Hosting hints — vercel.json, netlify.toml, wrangler.toml, Dockerfile, nginx configs.

The agent reports findings as a short summary, then proceeds to Phase 0.5.

Phase 0.5 — Dynamic content audit (deterministic, no LLM guesswork)

Read the full file on GitHub · 1,143 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.

  1. 9d ago First seen · 1,143 lines · 0 tokens per session scan B 07991a6110e2

Subscribe to this mod's changes

seo-pro-max is a cursor rule published in the GitHub repository aycanozarpaci/seo-pro-max-skill (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 20,586 tokens. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.