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 skills/bytefer/geo-seo-codex/geo-platform-optimizernpx skills add bytefer/geo-seo-codex --skill geo-platform-optimizergit clone --depth 1 https://github.com/bytefer/geo-seo-codexWrote 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/bytefer/geo-seo-codex/geo-platform-optimizer)<a href="https://agentmods.dev/skills/bytefer/geo-seo-codex/geo-platform-optimizer"><img src="https://agentmods.dev/badge/skills/bytefer/geo-seo-codex/geo-platform-optimizer.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.1 | $0.00034 | $0.04455 |
| Opus 5 | $0.00017 | $0.02227 |
| Sonnet 5 | $0.00007 | $0.00891 |
| Haiku 4.5 | $0.00003 | $0.00445 |
Grade A, and why
geo-platform-optimizer 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 6d 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.
This is a copy
100% identical to geo-platform-optimizer — 6 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Platform Optimizer
Core Insight
Only 11% of domains are cited by BOTH ChatGPT and Google AI Overviews for the same query. Each AI search platform uses different indexes, ranking logic, and source preferences. A page optimized for Google AI Overviews may be invisible to ChatGPT, and vice versa. Platform-specific optimization is not optional — it is the foundation of any serious GEO strategy.
How to Use This Skill
- Collect the target URL and the site's primary topic/industry
- Run each platform checklist below against the site
- Score each platform on the 0-100 rubric
- Generate GEO-PLATFORM-OPTIMIZATION.md with per-platform scores, gaps, and action items
Platform 1: Google AI Overviews (AIO)
How AIO Selects Sources
- 92% of AIO citations come from pages already ranking in the top 10 organic results — traditional SEO is the gateway
- However, 47% of citations come from pages ranking below position 5 — AIO has its own selection logic favoring clarity and directness over raw rank
- AIO strongly favors pages with clean structure, direct answers, and scannable formatting
- Featured snippet optimization has ~70% overlap with AIO optimization
- AIO prefers concise, factual, unambiguous answers — hedging and filler reduce citation probability
Optimization Checklist
- Question-Based Headings: Use H2/H3 headings phrased as questions matching real user queries. Check Google's "People Also Ask" for the target topic and mirror those exact phrasings.
- Direct Answer in First Paragraph: After each question heading, provide a clear 1-2 sentence answer immediately. Then expand with supporting detail. The first sentence should be a standalone citation candidate.
- Tables and Structured Comparisons: AIO heavily cites tables. Convert any comparison, pricing, specification, or feature data into HTML tables. Use clear column headers.
- Ordered and Unordered Lists: Step-by-step processes should use ordered lists. Feature lists should use unordered lists. AIO extracts these directly.
- FAQ Sections: Add a dedicated FAQ section with 5-10 real questions. Use proper H3 headings for each question. While FAQPage schema rich results are restricted to govt/health sites since Aug 2023, the content pattern still helps AIO extraction.
- Definitions and Glossary Boxes: For any industry-specific term, provide a clear definition. Format: "[Term] is [concise definition]." AIO frequently cites definitions.
- Statistics with Sources: Include specific numbers with attribution. "According to [Source], [statistic]." AIO prefers citeable, specific claims over vague assertions.
- Publication Date: Include a visible publication date and last-updated date. AIO deprioritizes undated content for time-sensitive queries.
- Author Byline: Display author name with credentials. Link to an author page with bio, credentials, and sameAs links.
- Page Depth: Keep target pages within 3 clicks of homepage. AIO rarely cites deep, orphaned content.
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.
- 6d ago First seen · 272 lines · 34 tokens per session scan A 766750180009
geo-platform-optimizer is a skill published in the GitHub repository bytefer/geo-seo-codex (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 4,455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to geo-platform-optimizer, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
building-edgespark-apps
Build and modify EdgeSpark apps. Use when a project has edgespark.toml, the user mentions EdgeSpark, or work involves the edgespark CLI, server SDK types, storage/auth/database workflows, deployment, or @edgespark/web.
edgespark-frontend-design
Design and redesign EdgeSpark frontends with distinctive, production-grade visual direction instead of generic AI-looking UI. Use when building or polishing landing pages, marketing sites, dashboards, auth flows, portfolios, product surfaces, or reusable frontend sections in EdgeSpark, especially when the task…
ppt-design-skill
Design, generate, review, and revise editable PowerPoint presentations through a rigorous brief-to-PNG workflow using the public pptx-designer Python library.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
execute
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.