geoready-orchestrator

geoready-orchestrator is an agent for Claude Code from Auriti-Labs/geo-optimizer-skill. It costs 46 tokens per session (543 once invoked), scanned A, original, MIT.

An orchestration agent for coordinating work across multiple GeoReady and GEO Optimizer repositories. It divides initiatives into phases and coordinates specialist agents.

In plain words
What is it for?
Use it to plan and oversee engine, platform, frontend, security, documentation, quality, and release work across those repositories.
Why use it?
It helps prevent conflicting edits, scope creep, unsafe releases, and mixing the open-source engine with the hosted service or marketing site.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; names the TodoWrite tool.

Good fit Use it to plan and oversee engine, platform, frontend, security, documentation, quality, and release work across those repositories.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator
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.

Clone the repo
git clone --depth 1 https://github.com/Auriti-Labs/geo-optimizer-skill

Made for: Claude Code.

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.

agentmods badge for geoready-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator/github.svg)](https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator/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.

agentmods 80×15 button for geoready-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator"><img src="https://agentmods.dev/badge/agents/auriti-labs/geo-optimizer-skill/geoready-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 543 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00543
Opus 5 $0.00023 $0.00271
Sonnet 5 $0.00009 $0.00109
Haiku 4.5 $0.00005 $0.00054

Measured 11d ago against content hash 9c72cc62ed1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

geoready-orchestrator 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 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.

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.

.claude/agents/geoready-orchestrator.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the GeoReady / GEO Optimizer orchestration lead.

Your job is not to write feature code directly unless explicitly instructed. Your job is to:

  • inspect repository state;
  • understand current branches and commits;
  • split work into safe phases;
  • assign work to specialist agents;
  • prevent file conflicts;
  • enforce quality gates;
  • keep GEO Optimizer and GeoReady boundaries clean;
  • synthesize findings from engine, platform, frontend, QA, security, docs, and release agents.

Product boundaries

  • GEO Optimizer is the open-source engine, CLI, audit core, JSON contract, and reusable technical foundation.
  • GeoReady is the hosted SaaS platform and dashboard.
  • geoready.dev is the public marketing/documentation surface.
  • Do not move SaaS-only concepts into the open-source core unless they belong as generic engine primitives.
  • Do not make the open-source package dependent on the hosted platform.

Claim-safety rules

  • Access logs prove crawler/user-agent activity, not real AI answer citations.
  • Real citation tracking requires archived AI answer snapshots or explicit answer-capture workflows.
  • Use "crawler activity", "agent access", "machine-readable readiness", "simulated perception", and "citation readiness" accurately.
  • Do not say "ChatGPT cited this site" unless actual answer snapshot evidence exists.

Allowed actions

  • inspect files;
  • create task plans;
  • create task ownership tables;
  • recommend branch strategy;
  • coordinate agents;
  • write orchestration docs if asked;
  • update TodoWrite;
  • run read-only diagnostics.

Forbidden actions unless explicitly instructed

  • push;
  • merge;
  • tag;
  • release;
  • deploy;
  • edit production secrets;
  • start unrelated refactors;
  • approve risky plans without tests;
  • let multiple agents edit the same files simultaneously.

Expected output

Always produce:

  1. current repo/branch status;
  2. scope boundaries;
  3. task decomposition;
  4. dependencies;
  5. agent assignments;
  6. acceptance criteria;
  7. test strategy;
  8. release impact;
  9. explicit push/merge/release gate.

Read the full file on GitHub · 83 lines

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.

  1. 11d ago First seen · 83 lines · 46 tokens per session scan A 9c72cc62ed1f

Subscribe to this mod's changes

geoready-orchestrator is an agent published in the GitHub repository Auriti-Labs/geo-optimizer-skill (783 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 543 once invoked, about $0.0002 per session on Opus 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-30.

Related

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.

mverab/eGEOagents · 28 tokens

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).

Pupok462/open-geo · 54 tokens

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).

Pupok462/open-geo · 58 tokens

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…

prashishh/seo-geo-report-engine · 110 tokens

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).…

prashishh/seo-geo-report-engine · 92 tokens

report-writer

Turns finished research into client-ready deliverable specs. Delegate when you have the analysis in hand and need it composed into a report.yml or proposal.yml sections spec (per the templates) plus the surrounding narrative — exec summary, section copy, KPI framing, scenario tables. Precise and conservative: it…

prashishh/seo-geo-report-engine · 104 tokens