arcgis-pro-automation

arcgis-pro-automation is a skill for Claude Code, Codex from muend/geoai-skills. It costs 159 tokens per session (1,520 once invoked), scanned A, original, MIT.

A way to control local ArcGIS Pro projects and ArcPy geoprocessing tasks through a guarded background connection. ArcGIS Pro is desktop software for making and analysing maps.

In plain words
What is it for?
It helps inspect ArcGIS projects and geodatabases, run spatial and raster operations, edit data, apply map styling, and export layouts.
Why use it?
It allows repeatable local processing while checking paths, permissions, licensing, and actual results instead of assuming a project or dataset changed.

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 inspect ArcGIS projects and geodatabases, run spatial and raster operations, edit data, apply map styling, and export layouts.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/muend/geoai-skills/arcgis-pro-automation"><img src="https://agentmods.dev/badge/skills/muend/geoai-skills/arcgis-pro-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 159 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,520 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.00159 $0.01520
Opus 5 $0.00079 $0.00760
Sonnet 5 $0.00032 $0.00304
Haiku 4.5 $0.00016 $0.00152

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

Security

Grade A, and why

arcgis-pro-automation 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 12d 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/arcgis-pro-automation/SKILL.md · 113 lines

How it starts

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

ArcGIS Pro Automation

Operate saved ArcGIS Pro projects and local GIS datasets through the guarded arcgis-mcp-bridge tool surface. Treat the bridge as an execution backend, not as permission to mutate data or claim a result that was never observed.

Establish the boundary

  • Require Windows, a licensed ArcGIS Pro installation, and a bridge worker interpreter that can import ArcPy for real geoprocessing.
  • Use the bridge for local, headless, repeatable ArcPy work. It does not drive the visible ArcGIS Pro UI and does not administer ArcGIS Online or Enterprise.
  • If the bridge tools are not callable, provide setup or a dry execution plan. Never simulate tool output or imply that an .aprx or .gdb changed.
  • Use the schemas exposed by the connected MCP server. Tool names may be host- namespaced; match the semantic catalog name and never invent parameters.
  • Keep every read and write inside the configured allowed roots. Use absolute paths and a dedicated scratch geodatabase for intermediate outputs.

Read runtime and licensing before the first execution or whenever setup, extension availability, or worker failures are in scope.

Execute the workflow

  1. Define the contract. Identify inputs, intended output artifacts, CRS and units, whether a saved .aprx must change, and which operations create, overwrite, append, or edit data.
  2. Preflight. Call health_check first. Inspect its worker interpreter, allowed roots, scratch GDB, timeout, and concurrency. Because this call does not import ArcPy, follow it with a non-mutating ArcPy-backed request such as get_spatial_reference, describe_dataset, or list_layers before treating the runtime as execution-ready.
  3. Inspect before acting. Read dataset descriptions, counts, fields, CRS, extents, project maps/layers, and required extension licenses. Resolve datum transformations, units, and output naming before analysis.
  4. Plan exact tools. Select the smallest declarative sequence from tool routing. Separate read-only inspection, new-output creation, and in-place mutation. Prefer new outputs and working copies over edits to source data.
  5. Authorize mutations. Read safety and validation before any write. Set confirm=true only when the user's request clearly authorizes the exact mutating operation and target. Treat overwrite=true as a separate explicit decision. Stop on ambiguous target, scope, or intent.
  6. Execute incrementally. Run one dependent step at a time; preserve returned output paths and geoprocessing messages. Parallelize only independent jobs when license seats, memory, and max_workers are known to support them.
  7. Verify independently. Re-open outputs and test the relevant invariants: existence, count, geometry validity, CRS and units, raster statistics and NoData, network solve status, project contents, or exported layout dimensions. A success status alone is not evidence of a correct GIS result.

Read the full file on GitHub · 113 lines

Files

What ships with it

5 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. 12d ago First seen · 113 lines · 159 tokens per session scan A 2ba2568f7045

Subscribe to this mod's changes

arcgis-pro-automation is a skill published in the GitHub repository muend/geoai-skills (18 stars, last pushed 8d ago), licensed MIT. It adds 159 tokens to every session and 1,520 once invoked, about $0.0008 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.