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 imisic/claude-marketplace --skill a-geo-optimizergit clone --depth 1 https://github.com/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/a-geo-optimizer)<a href="https://agentmods.dev/skills/imisic/claude-marketplace/a-geo-optimizer"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/a-geo-optimizer/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/imisic/claude-marketplace/a-geo-optimizer"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/a-geo-optimizer.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.00156 | $0.02074 |
| Opus 5 | $0.00078 | $0.01037 |
| Sonnet 5 | $0.00031 | $0.00415 |
| Haiku 4.5 | $0.00016 | $0.00207 |
Grade A, and why
a-geo-optimizer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
7. **Don't block crawlers by accident**: Always check the LIVE robots.txt for inherited CMS/CDN blocks on AI user-agents, injected Content-Signal directives (Cloudflare's managed robots.txt defaults to `ai-train=no` on 3 How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Optimizer: AI Search Visibility Skill
Make any web project discoverable and citable by AI assistants (ChatGPT, Claude, Gemini, Perplexity, Copilot). This skill covers technical implementation, content structure, and ongoing monitoring.
When to use this skill
- New site/page creation: Bake GEO in from the start
- Existing site audit: Diagnose and fix AI visibility gaps
- Content writing/restructuring: Format content for AI citation
- Template development: Build PHP/HTML templates with GEO built-in
- robots.txt / schema / sitemap work: Ensure AI crawler compatibility
- Competitive analysis: Compare AI citation performance
How to use this skill
Step 1: Determine the task type
Ask yourself which mode applies:
| Mode | When | What to do |
|---|---|---|
| Full audit | User wants the full review | Run all checklists from references/technical-checklist.md |
| New build | Creating a site/page from scratch | Follow the build-time integration guide below |
| Content optimization | Writing or restructuring content | Follow references/content-strategy.md |
| Quick fix | Specific technical task (robots.txt, schema, etc.) | Jump to relevant section in references/technical-checklist.md |
Step 2: For full audits, follow this sequence
- Technical foundation: Read
references/technical-checklist.mdand verify:- robots.txt allows AI crawlers (exact user-agents in
references/crawler-reference.md) - Server-side rendering (critical: most AI crawlers don't execute JS)
- Schema.org JSON-LD markup on key pages
- Page speed (FCP < 0.4s target)
- XML sitemap + RSS/Atom feed
- HTTPS, mobile-friendly
- llms.txt file: if present it MUST pass Lighthouse validation (H1 + markdown
[text](url)links, see checklist section 5); a malformed one is worse than none because it fails a visible audit - Agentic Browsing readiness (checklist section 13): run PageSpeed Insights and read the Agentic Browsing category; agent-critical a11y (programmatic names, valid ARIA, touch targets) and CLS now double as agent-readiness signals. WebMCP only matters for interactive sites (search, cart, booking)
- If behind Cloudflare: fetch the LIVE robots.txt and check for injected Content-Signal directives (
ai-train=nois the managed default;ai-input=nowould hurt AI citation, see crawler-reference section 12)
- robots.txt allows AI crawlers (exact user-agents in
What ships with it
4 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.
- 11d ago First seen · 142 lines · 156 tokens per session scan A 5bbf07035735
a-geo-optimizer is a skill published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 9d ago), licensed MIT. It adds 156 tokens to every session and 2,074 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agentic-review
Deep multi-agent code review for local changes. Inspired by AmpCode's agentic review. Use when you want comprehensive analysis of staged changes, unstaged changes, specific commits, or branch differences. Spawns parallel specialized agents (security, performance, patterns, architecture) and synthesizes actionable…
qa
Full QA on all session changes using Codex as a second pair of eyes. Use when user says "QA", "full QA", "QA my changes", "QA all your changes", or "use codex to review". Runs git diff, sends changes to Codex for thorough review, and synthesizes findings.
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
rubber-ducky
Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke holes in this", "what am…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…