ras-commander: Agent for Claude Code

.claude/agents/rasmapper-spatial-reviewer.md

rasmapper-spatial-reviewer is an agent for Claude Code from gpt-cmdr/ras-commander. It costs 89 tokens per session (907 once invoked), scanned A, original, MIT.

A review assistant for HEC-RAS RASMapper, the map viewer used to inspect river and flood models. It creates map views, opens RASMapper, captures screenshots, and explains what the images show.

In plain words
What is it for?
Use it to review 2D flow areas, lateral structures, breaklines, terrain context, and selected geometry features such as structures or cross sections.
Why use it?
It makes spatial model checks repeatable and records visual evidence instead of relying on manual inspection. This helps reveal when a map does not prove the finding being claimed.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is gpt-cmdr/ras-commander's own configuration. It tells Claude Code how to work on ras-commander itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ras-commander configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/gpt-cmdr/ras-commander/main/.claude/agents/rasmapper-spatial-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/gpt-cmdr/ras-commander

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 rasmapper-spatial-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/rasmapper-spatial-reviewer.svg)](https://agentmods.dev/agents/gpt-cmdr/ras-commander/rasmapper-spatial-reviewer)
Your own site
<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>
Per session 89 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 907 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.00089 $0.00907
Opus 5 $0.00044 $0.00453
Sonnet 5 $0.00018 $0.00181
Haiku 4.5 $0.00009 $0.00091

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

Security

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.

.claude/agents/rasmapper-spatial-reviewer.md · 129 lines

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

  1. Prefer ras-commander public APIs over direct XML edits.
  2. Use ras.rasmap_df, RasMap.list_map_layers(), and RasMap.list_geometry_layers() for discovery.
  3. Prefer RasMap.create_spatial_review_package() when the task needs a repeatable QA artifact.
  4. Use RasMap.list_geometry_features() and feature selectors when the user asks for one structure, breakline, flow area, or cross section.
  5. Keep terrain visible for spatial QA screenshots unless the user asks for a non-terrain view.
  6. Enable RasMap.set_update_legend_with_view() before capturing terrain or result surface screenshots.
  7. Keep RASD2FlowArea visible when inspecting LateralStructureLayer or similar structure/breakline targets.
  8. Zoom with RasMap.zoom_to_geometry_layer() when the target has HDF-derived extents.
  9. Store outputs in working/rasmapper_spatial_review/ or a user-provided review folder.

Evidence Standard

Every finding needs traceable evidence:

  • project path
  • .rasmap path
  • 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 data
  • Likely - visible in screenshot but needs numerical confirmation
  • Uncertain - plausible but screenshot or data is insufficient

Read the full file on GitHub · 129 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. 7d ago First seen · 129 lines · 89 tokens per session scan A 2ce0a025a401

Subscribe to this mod's changes

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.