GEO Optimizer is a toolkit that checks whether AI answer services such as ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews can find, interpret, and cite a website. It helps people audit and improve a site's visibility in AI-generated answers through a command-line tool, Python library, MCP server, GitHub Action, or Astro integration.
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.
git clone --depth 1 https://github.com/Auriti-Labs/geo-optimizer-skillWrote 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/agents/auriti-labs/geo-optimizer-skill/team_usage)<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/team_usage"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/team_usage/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/agents/auriti-labs/geo-optimizer-skill/team_usage"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/team_usage.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.00000 | $0.01405 |
| Opus 5.5 | $0.00000 | $0.00562 |
| Sonnet 5.5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
TEAM_USAGE 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Usage Guide
GeoReady / GEO Optimizer
1. Agent inventory
| Agent | Role | Writes code? | Worktree isolation | Use before impl? | Use after impl? |
|---|---|---|---|---|---|
geoready-orchestrator |
Coordination lead | No | No | Yes (required) | Yes (synthesis) |
geo-engine-architect |
Engine/CLI/JSON | Yes | Yes | Yes (design) | Yes (review) |
geoready-platform-api |
Backend/API/DB | Yes | Yes | Yes (design) | Yes (review) |
geoready-dashboard-ui |
Dashboard/frontend | Yes | Yes | Yes (design) | Yes (review) |
geo-qa-verifier |
QA/testing | No* | No | No | Yes (required) |
geo-security-privacy-reviewer |
Security/privacy | No | No | Yes | Yes |
geo-product-docs-release |
Docs/copy/release | Yes | Yes | No | Yes |
geo-roadmap-release-manager |
Versioning/release | No | No | Yes (planning) | Yes (release gate) |
geo-wordpress-connector-architect |
WP connector arch | Yes | Yes | Yes (spec only) | Yes (review) |
*geo-qa-verifier may apply minimal fixes only if explicitly instructed and fix is directly tied to a QA finding.
2. Read-only reviewers
These agents should not modify product code:
geoready-orchestratorgeo-qa-verifiergeo-security-privacy-reviewergeo-roadmap-release-manager
3. Code-writing implementation agents
These agents may edit/write code (use worktree isolation):
geo-engine-architect—geo-optimizer-skill/geoready-platform-api—geoready-platform/backend/geoready-dashboard-ui—geoready-platform/frontend/geo-product-docs-release— README, CHANGELOG, docs/, copygeo-wordpress-connector-architect— plugin skeleton (only if approved)
4. Agents that should run before implementation
geoready-orchestrator— always first; produces plan and agent assignmentsgeo-roadmap-release-manager— confirm SemVer impact and release scopegeo-security-privacy-reviewer— identify security requirements before buildinggeo-engine-architect— design engine API/contract before platform builds against it
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.
- 1mo ago First seen · 147 lines · 0 tokens per session scan A 1852dde2ae64
TEAM_USAGE is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (1,136 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,405 tokens. 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-30.
Other agents, from other repositories
geo-ranker
Simulates AI-engine ranking to evaluate content quality. Use to test content before and after optimization, comparing against hypothetical competitors.
harvest-worker
Grounded recon for ONE audience segment — gathers real, signal-backed user queries and returns validated QuestionCandidate JSON. Never writes questions.csv, never touches the DB. Spawned by the open-geo orchestrator (STEP A.5, Phase A).
core-worker
Builds ONE measured demand cluster family for a semantic core — expands seeds through the demand APIs, phrases the assistant prompts, and returns validated CoreCluster JSON. No browser, never writes the core or the CSV. Spawned by the semantic-core orchestrator (STEP 4).
geo-analyst
AI-search / GEO specialist. Delegate when the question is about visibility inside AI answers (ChatGPT, Perplexity, Google AI Overviews/AI Mode, Claude, Copilot): brand share-of-voice and mentions over time, which domains/pages the models cite, what AI actually says about the brand, page citability, llms.txt, and…
seo-analyst
Technical, on-page, keyword, and rank analyst. Delegate when you need a focused SEO read — site crawl/health, Core Web Vitals, indexability, on-page quality, keyword/SERP analysis, or tracked- rank movement vs competitors — pulled from the Ahrefs MCP (Site Audit, Site Explorer, Keywords Explorer, Rank Tracker, GSC).…
geo-content
Content quality specialist evaluating E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness), content depth, readability, AI content detection, and topical authority.