geoai-orchestrator

geoai-orchestrator is a skill for Claude Code, Codex from muend/geoai-skills. It costs 109 tokens per session (2,293 once invoked), scanned A, original, MIT.

A coordinator for complex geospatial work, meaning work with data tied to places on Earth. It sends each stage to the appropriate specialist and keeps shared checks consistent.

In plain words
What is it for?
It helps plan end-to-end workflows that may combine data collection, satellite imagery, modelling, spatial analysis, and map delivery.
Why use it?
It prevents multi-stage projects from using conflicting coordinate systems, units, validity rules, or unverified results.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the geoai plugin — 18 skills shipped together

Good fit It helps plan end-to-end workflows that may combine data collection, satellite imagery, modelling, spatial analysis, and map delivery.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muend/geoai-skills/geoai-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.

Any agent
npx skills add muend/geoai-skills --skill geoai-orchestrator
Clone the repo
git clone --depth 1 https://github.com/muend/geoai-skills

Made for: Claude Code, Codex.

Or install geoai, the plugin that ships this one along with the rest of its 18 skills.

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 geoai-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/muend/geoai-skills/geoai-orchestrator/github.svg)](https://agentmods.dev/skills/muend/geoai-skills/geoai-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/muend/geoai-skills/geoai-orchestrator"><img src="https://agentmods.dev/badge/skills/muend/geoai-skills/geoai-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 geoai-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/muend/geoai-skills/geoai-orchestrator"><img src="https://agentmods.dev/badge/skills/muend/geoai-skills/geoai-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,293 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 160
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00109 $0.02293
Opus 5 $0.00055 $0.01146
Sonnet 5 $0.00022 $0.00459
Haiku 4.5 $0.00011 $0.00229

Measured 13d ago against content hash 6925301bb441, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

geoai-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 13d 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.

skills/geoai-orchestrator/SKILL.md · 171 lines

How it starts

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

GeoAI Orchestrator

The hub of an 18-skill geospatial module. Activate it for routing or pipeline composition, not as a mandatory wrapper around every spatial task. Its job: (1) diagnose what kind of spatial problem the user actually has, (2) design the pipeline across stages, (3) route each stage to the right specialist skill, and (4) enforce the module-wide invariants that every stage must obey.

Routing gate — read before producing any output

This orchestrator routes by invoking, never by naming. The gate below overrides every other section of this document, including the pipeline template.

  1. Invoke, do not list. Every specialist you select must be invoked with the Skill tool in the same response that selects it. Naming a skill in a table, plan, or prose sentence is not a handoff. A response that identifies the right specialist but does not invoke it has failed this skill's core function, no matter how accurate the diagnosis is.
  2. Route every correction, not the first one. When a request contains multiple findings, defects, or stages, each one gets its own routing decision and its own invocation. Routing one item and handling the rest inline is a partial failure; the count of routed items must equal the count of items found.
  3. Never make routing conditional on permission. Do not write "say the word and I'll route", "I can hand this off if you want", "let me know and I'll bring in the specialist", or any equivalent. Offering to route later is the single most common failure of this skill. If you have identified the specialist, invoke it now.
  4. Clarification is not a substitute for routing. Missing detail about scope (which deliverable, which study area) does not block routing of the stages you have already identified. Ask the scope question and route in the same response. Only a request whose entire domain is undetermined may be routed-free, and then you must say which specialist becomes available under each candidate answer.
  5. Audit requests are deliver requests. "Audit this plan", "review this pipeline", "what is wrong with this workflow" require the completed audit, the routed corrections, and the revised plan in one response. Do not return findings and hold the corrections back for a follow-up turn.

Read the full file on GitHub · 171 lines

Files

What ships with it

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

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. 13d ago First seen · 171 lines · 109 tokens per session scan A 6925301bb441

Subscribe to this mod's changes

geoai-orchestrator is a skill published in the GitHub repository muend/geoai-skills (18 stars, last pushed 9d ago), licensed MIT. It adds 109 tokens to every session and 2,293 once invoked, about $0.0005 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-31.