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 skills add aycanozarpaci/seo-pro-max-skill --skill seo-pro-maxgit clone --depth 1 https://github.com/aycanozarpaci/seo-pro-max-skillWrote 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/aycanozarpaci/seo-pro-max-skill/seo-pro-max)<a href="https://agentmods.dev/skills/aycanozarpaci/seo-pro-max-skill/seo-pro-max"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/aycanozarpaci/seo-pro-max-skill/seo-pro-max"><img src="https://agentmods.dev/badge/skills/aycanozarpaci/seo-pro-max-skill/seo-pro-max.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.00087 | $0.20646 |
| Opus 5 | $0.00044 | $0.10323 |
| Sonnet 5 | $0.00017 | $0.04129 |
| Haiku 4.5 | $0.00009 | $0.02065 |
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 11d 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. This is a copy
100% identical to seo-pro-max — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,142 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:
- 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. - Rendering model — SSR / SSG / SPA / hybrid / RSC / ISR.
- Routing convention — file-based (
app/,pages/,src/routes/,src/pages/) vs. controller-based (Laravelroutes/web.php, Djangourls.py, Express routers). - Existing SEO surface — any current
<head>management,metadataexports,Helmet,next/head,useSeoMeta, blade@section('meta'), etc. - Admin panel — presence of a backoffice (
app/(admin),admin/,/dashboard, Filament, Nova, Django admin, Strapi, custom). - Database — ORM (Prisma, Drizzle, Sequelize, TypeORM, Eloquent, Django ORM), migrations folder, existing settings/options table.
- i18n —
next-intl,next-i18next,vue-i18n,nuxt-i18n, Laravel locales, Django i18n. - 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)
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.
- 11d ago First seen · 1,142 lines · 87 tokens per session scan B 0dbea9b38112
seo-pro-max is a skill published in the GitHub repository aycanozarpaci/seo-pro-max-skill (7 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 20,646 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). It is 100% identical to seo-pro-max, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…