A page-improvement guide that compares a page or draft with the pages AI cites for its target questions.

Use it to improve a page for tracked prompts, cover related questions, fix site-audit issues, and make changes aimed at being cited by AI.

It turns citation gaps, missing answers, structured-data problems, and audit failures into a ranked list of changes.

optimize — Skill for Claude Code and Codex by ai-search-guru

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.

Any agent

npx skills add ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool --skill optimize

Clone the repo

git clone --depth 1 https://github.com/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize/github.svg)](https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize)

Your own site

<a href="https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize"><img src="https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize"><img src="https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 558 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.00558
Opus 5.5	$0.00009	$0.00223
Sonnet 5.5	$0.00005	$0.00112
Haiku 4.5	$0.00002	$0.00056

Measured yesterday against content hash cc9320c5b1af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

optimize 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

optimize — 92% identical, 0 lines differ

skills/optimize/SKILL.md · 50 lines

What it actually says

Optimize content

The playbook of the /optimize shortcut ("Optimize this page: …"): how one page or draft compares with what AI cites for its prompts, and the changes that would close the gap.

Data plan

Read only these, for the page or draft the person names:

fetch_page for the page, or get_draft for a draft (list_drafts to find it by name).
list_prompts and get_prompt_performance: the tracked prompts the page should win.
list_citations for those prompts over the last 30 days, and fetch_page for the one or two pages AI cites most.
get_fanouts: what the engines search for behind those prompts.
get_site_audit_summary and list_site_audit_issues: the page's latest Site Audit result, when it has one.

Use list_brands only when no brand is selected, and open_page to link the Content Editor.

Questions

When no tracked prompt fits the page, ask which prompts it should win, with two to four of the closest as options.

Steps

Score the page against the cited pages: does it answer the prompts directly, cover the fan-outs, carry structured data, and pass its audit checks?
List the changes, most impact first: what to change, where, and why AI would cite it after.
Write the changed passages, ready to paste, and the structured data as code.
When the person wants a draft changed, use update_draft; for a live page, save the new version with create_draft. The app asks them first when it should. In an agent's run nobody is there to ask: always save it with its tool, and the app holds it for approval where the agent's mode needs it.

Output

A change list: Change, Where, Why it helps AI answers, then the rewritten passages.

Next moves

Two or three, such as opening the page in the Content Editor, or generating its schema.

Don't

Never publish or change the live site: going live is always the person's click.
Never promise rankings or citations.

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.

yesterday First seen · 50 lines · 23 tokens per session scan A cc9320c5b1af

Subscribe to this mod's changes

optimize is a skill published in the GitHub repository ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool (449 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 558 once invoked, about $0.0001 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-11-05.

Marketing and SEO Writing and docs ai-search-optimization answer answer-engine-optimization chatgpt claude generative-engine-optimization

optimize next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
optimizeai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool	Skill	449	yesterday	MIT	A	23	Claude Code, Codex
geo-platform-optimizerasale-ai/seo-geo-skill	Skill	6	2mo ago	none	A	34	Claude Code
ansvisor-aeo-coach-standaloneansvisor/ansvisor	Skill	232	yesterday	MIT	A	148	Claude Code, Codex
geo-loopmverab/eGEOagents	Skill	217	yesterday	MIT	A	62	Claude Code
content-scoringmverab/eGEOagents	Skill	217	yesterday	MIT	A	34	Claude Code
competitive-analysismverab/eGEOagents	Skill	217	yesterday	MIT	A	29	Claude Code
schema-generatormverab/eGEOagents	Skill	217	yesterday	MIT	A	35	Claude Code