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 oegeyilmaz9/seo-aeo-geo-ultimate --skill seo-plangit clone --depth 1 https://github.com/oegeyilmaz9/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-plan)<a href="https://agentmods.dev/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-plan"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-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-plan"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-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.00053 | $0.00695 |
| Opus 5.5 | $0.00021 | $0.00278 |
| Sonnet 5.5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
seo-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 22d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Strategy and Delivery Plan
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.
Lane outputs: roadmap.md; dependencies.md (combine small related steps with stable section links). Sequence query decisions, source content, inventory/maps, routing, parity review, local acceptance, authorized release and full delivery checks. Preserve both keyword ambition tracks, maintenance owners and direct document links.
Purpose
Turn validated evidence and approved actions into a delivery roadmap that a team can execute and review. This skill coordinates scope, sequencing, and measurement; it does not create technical/content facts, approve releases, or promise business outcomes.
Read references/roadmap-protocol.md before planning a cross-team program.
Input gate
Require current business goal, audience/market, constraints, owners/capacity, validated audit/research artifacts, approved action-plan items, baseline/report availability, and known dependencies. When inputs are incomplete, produce a discovery plan with explicit assumptions—not a fabricated quarter-long backlog.
Workflow
- Frame decisions. State the goal, target audience/market, change scope, non-goals, risk tolerance, and measures that are actually available.
- Use validated work only. Include confirmed issues and approved actions. Keep experimental work in a separate learning track. Declined/risky changes remain visible with their conditions.
- Sequence dependencies. Establish source data, site prerequisites, content/technical dependencies, product decision, separate implementation/release/provider approvals, rollout, verification, and rollback before downstream work. For compound work, preserve the router's chain from research and baseline through local acceptance, authorized release, live verification, any separately authorized provider operation, and delayed comparison. For broad organic growth, preserve two concurrent roadmap tracks: nearer-term capture/defense and high-volume head-term/category leadership. Put the leadership track's owner and foundation work into the active roadmap even when authority building and leading-position milestones span later stages; do not replace it with quick wins.
- Assign outcomes honestly. Give each initiative owner, acceptance criteria, verification method, guardrail, and review date. A roadmap may target a measurable behavior, but cannot forecast rankings, citations, traffic, or revenue as a guarantee.
- Report changes. Compare only like-for-like observations. Separate delivery status, technical state, search reporting, visibility observations, referrals, and conversions.
What ships with it
3 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.
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.
- 22d ago Changed · +7 lines e3393cab53ff
- 1mo ago First seen · 30 lines · 53 tokens per session scan A bc4624e29ed3
seo-plan is a skill published in the GitHub repository oegeyilmaz9/seo-aeo-geo-ultimate (5 stars, last pushed 22d ago), licensed Apache-2.0. It adds 53 tokens to every session and 695 once invoked, about $0.0002 per session on Opus 5.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
backlink-outreach
Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics…
content-thicken
Evidence-driven blog driver. Takes ONE target from the fused search plus AI-answer content library, pulls the real questions it has to answer, drafts a thick long-form guide against a template contract, validates it deterministically, and stops at preview. Two modes, thicken an already-earning post IN PLACE (never…
geo-monitor
Run and read the GEO pipeline, which measures whether AI answer engines mention, recommend and cite your site. Puts a fixed registry of real user questions to an answer engine through the Monid tool layer, detects the three signals plus competitors, and turns "a rival is named and we are not" into a tracked work…
seo-intake
Run and read the SEO intake pipeline. Pulls the organic keyword set for your domain and for each competitor through the Monid tool layer, computes the gap locally, and routes every keyword to the one action that can help it (write-new / striking / build-depth / defend / noise). Use when asked to refresh the SEO queue…
bytesagain-geo-seo
GEO SEO — Generative Engine Optimization reference. Complete guide for optimizing websites for AI search engines. Covers llms.txt spec, GEO checklist, automated scanning, AI bot tracking with nginx, AEO (Answer Engine Optimization) for getting cited by ChatGPT/Perplexity/Gemini, citation monitoring, and content…
geo-content-research
Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.