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 oegeyilmaz9/seo-aeo-geo-ultimate/plugin install seo-aeo-geo-ultimateWrote 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/oegeyilmaz9/seo-aeo-geo-ultimate/seo-action-plan)<a href="https://agentmods.dev/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-action-plan"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-action-plan/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/oegeyilmaz9/seo-aeo-geo-ultimate/seo-action-plan"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-action-plan.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.00042 | $0.01498 |
| Opus 5 | $0.00021 | $0.00749 |
| Sonnet 5 | $0.00008 | $0.00300 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
seo-action-plan 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Action Plan
Purpose
Turn evidence-backed findings into a sequenced implementation plan that a content, engineering, analytics, product, or legal owner can approve and execute. This skill plans work; it does not change a site, publish content, modify crawler controls, deploy code, or approve its own recommendations.
Use it after seo-aeo or seo-geo has produced a validated optimization-brief.json, or after a conventional SEO specialist has produced a validated seo-findings.json bundle. For a normal conversational audit without a validated artifact, provide a clearly labelled provisional action list and name the evidence needed before it becomes a formal plan.
Non-negotiable boundaries
- Do not promise inclusion, ranking, citation, referral, traffic, revenue, or conversion lift.
- Do not invent a platform requirement. In particular, do not prescribe
llms.txt, special “AI schema”, chunk sizes, bot access, or a crawler-control change unless the supplied evidence and the applicable platform documentation support it. - Separate an observed issue from its likely cause and from the proposed change.
- Never treat a crawler request or bot log as evidence of retrieval, grounding, citation, referral, or conversion.
- Do not turn a speculative or experimental finding into a normal implementation action. Keep it as a monitored experiment or decline it.
- Require human approval for production, policy, legal, accessibility, analytics, or crawler-control changes. The plan’s approval status starts as
pending.
Formal-plan workflow
Read references/action-plan-protocol.md before creating action-plan.json.
-
Check the input gate. Require an immutable, validated upstream bundle. An AEO/GEO input contains
optimization-brief.json,research-pack.json, and its referenced raw evidence. A conventional SEO input containsseo-findings.jsonand the raw evidence it names. Run:Let
<suite-root>mean${CLAUDE_PLUGIN_ROOT}in Claude Code. In Codex, read.seo-suite-runtime.jsonbeside thisSKILL.mdwhen present and use itssuite_rootvalue; otherwise use the absolute repository checkout, then run:
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 202 B
- references/action-plan-protocol.md 5.1 KB
- references/contracts/action-plan.schema.json 10 KB
- references/contracts/contracts-lock.json 2.5 KB
- references/contracts/evidence-record.schema.json 1.7 KB
- references/contracts/optimization-brief.schema.json 6.3 KB
- references/contracts/research-pack.schema.json 5.2 KB
- references/contracts/seo-findings.schema.json 5.2 KB
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 · 92 lines · 42 tokens per session scan A 7927b8ad04ff
seo-action-plan is a skill published in the GitHub repository oegeyilmaz9/seo-aeo-geo-ultimate (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,498 once invoked, about $0.0002 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
ansvisor-aeo-coach-standalone
Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution. For clients that support…
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
ansvisor-aeo-coach
Acts as an Answer Engine Optimization (AEO) analyst for users running Ansvisor. Activates when the user asks how their brand is doing across AI search engines (ChatGPT, Gemini, Perplexity, Claude, Copilot, AI Overview, AI Mode), why visibility changed, or how they compare to competitors. Uses the Ansvisor MCP server…
seo-fix-apply
Writer protocol preloaded into the seo-fixer-writer agent — how confirmed SEO/AI-search fixes are applied (git pre-flight, backup, Edit/Write for local diffs, ticketed adapter CLIs for remote targets, re-verify, publish only on a second ticket, rollback) and the findings-array output contract. Used only by the fix…
audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured…
orangeo-ai-visibility-skill
Audit brand AI visibility readiness and prepare OranGEO-style GEO, AEO, LLM SEO, and AI search optimization action plans. Use when asked for a Claude Code skill, Codex skill, GEO skill, generative engine optimization skill, answer engine optimization skill, AI visibility audit, AI search visibility checker, llms.txt…