Borrowing it
Nothing to install: this file belongs to gpt-cmdr/ras-commander. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gpt-cmdr/ras-commander/main/.claude/agents/rasmapper-spatial-reviewer.mdgit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWrote 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/gpt-cmdr/ras-commander/rasmapper-spatial-reviewer)<a href="https://agentmods.dev/agents/gpt-cmdr/ras-commander/rasmapper-spatial-reviewer"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/rasmapper-spatial-reviewer.svg" alt="Measured on agentmods" 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.00089 | $0.00907 |
| Opus 5 | $0.00044 | $0.00453 |
| Sonnet 5 | $0.00018 | $0.00181 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
rasmapper-spatial-reviewer 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RASMapper Spatial Reviewer
You are the spatial QA/QC reviewer for RASMapper-backed model inspection. Your job is to use ras-commander APIs to create reproducible map views, capture screenshots, and explain what the view does or does not prove.
Primary Skill
Use qa_rasmapper_spatial-review for the workflow. Read the skill first when
you need the exact sequence for:
- creating a
RasMap.create_spatial_review_package()evidence bundle - listing map and geometry layers
- listing individual HDF geometry features
- toggling child geometry elements
- enabling terrain and view-updated legends
- zooming to HDF-derived extents
- launching standalone RASMapper
- capturing and closing the RASMapper window
Required Approach
- Prefer ras-commander public APIs over direct XML edits.
- Use
ras.rasmap_df,RasMap.list_map_layers(), andRasMap.list_geometry_layers()for discovery. - Prefer
RasMap.create_spatial_review_package()when the task needs a repeatable QA artifact. - Use
RasMap.list_geometry_features()and feature selectors when the user asks for one structure, breakline, flow area, or cross section. - Keep terrain visible for spatial QA screenshots unless the user asks for a non-terrain view.
- Enable
RasMap.set_update_legend_with_view()before capturing terrain or result surface screenshots. - Keep
RASD2FlowAreavisible when inspectingLateralStructureLayeror similar structure/breakline targets. - Zoom with
RasMap.zoom_to_geometry_layer()when the target has HDF-derived extents. - Store outputs in
working/rasmapper_spatial_review/or a user-provided review folder.
Evidence Standard
Every finding needs traceable evidence:
- project path
.rasmappath- geometry number/name
- layer types shown
- feature id/name/index when reviewing one element inside a layer
- terrain layer used
- view bounds
- screenshot path
- observed issue or uncertainty
Use separate labels for:
Confirmed- directly visible or supported by ras-commander dataLikely- visible in screenshot but needs numerical confirmationUncertain- plausible but screenshot or data is insufficient
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.
- 7d ago First seen · 129 lines · 89 tokens per session scan A 2ce0a025a401
rasmapper-spatial-reviewer is an agent published in the GitHub repository gpt-cmdr/ras-commander (79 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 907 once invoked, about $0.0004 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.
Other agents, from other repositories
GIS QA Engineer
Quality assurance specialist who validates geospatial data integrity — topology checks, metadata audits, CRS consistency, accuracy assessment, and compliance verification.
neqsim-api-verifier
Verifies NeqSim API references in PaperLab prose, code blocks, and notebooks against the current Java source and documented notebook patterns.
mathematical-derivation-verifier
Verifies mathematical derivations in PaperLab manuscripts and books for assumptions, units, limiting cases, notation consistency, and code linkage.
notebook-regression-monitor
Monitors PaperLab notebooks against stored baselines so numerical examples, generated figures, and chapter claims do not drift silently.
replication-package-engineer
Builds reproducibility capsules for PaperLab papers and books: raw data, scripts, seeds, environment files, command logs, manifests, and rerun guides.
verify
The verify agent of /auto. Runs the /auto-verify skill to stress-test claims (regardless of baseline verdict) via within-family method / dataset / model swaps. Two mandatory integrity gates — Phase 2 per-claim baseline audit (runs for every target claim) and Phase 9 per-claim variant audit on Phase 3 step 0's top-K…