ras-commander: Agent for Claude Code

.claude/agents/hecras-project-inspector.md

hecras-project-inspector is an agent for Claude Code from gpt-cmdr/ras-commander. It costs 131 tokens per session (3,331 once invoked), scanned A, original, MIT.

An analysis agent for HEC-RAS projects, which are engineering models used to simulate water flow and flooding. It uses the ras-commander Python API and project data tables to report structure, run status, boundary conditions, and issues.

In plain words
What is it for?
Use it to initialize a HEC-RAS project, inspect its plans, geometry, flows, boundaries, and results, and identify problems.
Why use it?
It turns project state into an actionable report without requiring manual inspection of project files.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; mentions AGENTS.md.

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/hecras-project-inspector.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 hecras-project-inspector

README.md
[![agentmods](https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/hecras-project-inspector/github.svg)](https://agentmods.dev/agents/gpt-cmdr/ras-commander/hecras-project-inspector)
Your own site
<a href="https://agentmods.dev/agents/gpt-cmdr/ras-commander/hecras-project-inspector"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/hecras-project-inspector/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 hecras-project-inspector

Your own site · 80×15
<a href="https://agentmods.dev/agents/gpt-cmdr/ras-commander/hecras-project-inspector"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/hecras-project-inspector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 131 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,331 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.00131 $0.03331
Opus 5 $0.00066 $0.01665
Sonnet 5 $0.00026 $0.00666
Haiku 4.5 $0.00013 $0.00333

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

Security

Grade A, and why

hecras-project-inspector 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 10d 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/hecras-project-inspector.md · 382 lines

How it starts

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

CRITICAL: API-First Mandate

This agent MUST use the ras-commander Python API as its primary tool.

Required Approach

  1. MUST call init_ras_project() first to populate DataFrames
  2. MUST use ras.plan_df, ras.geom_df, ras.boundaries_df for all project analysis
  3. MUST NOT use Explore subagent or Bash to inventory project files
  4. MUST NOT use ls, glob, Grep, or file system operations to find plans, geometries, or flows

Why This Matters

The DataFrames ARE the project intelligence. They provide:

  • Pre-parsed plan configurations and file relationships
  • HDF result paths indicating execution status
  • Complete boundary condition inventory with DSS references
  • File path validation already performed

Do not use Explore/Bash to inventory files -- this bypasses DataFrame intelligence and produces inferior, inconsistent results.

Correct Pattern

from ras_commander import init_ras_project, ras

# Initialize - this populates ALL DataFrames
init_ras_project("/path/to/project", "7.0")

# Project analysis via DataFrames (NOT file exploration)
total_plans = len(ras.plan_df)
executed_plans = ras.plan_df[ras.plan_df['HDF_Results_Path'].notna()]
pending_plans = ras.plan_df[ras.plan_df['HDF_Results_Path'].isna()]

# Boundary condition inventory
bc_summary = ras.boundaries_df.groupby('bc_type').size()
flow_bcs = ras.boundaries_df[ras.boundaries_df['bc_type'] == 'Flow Hydrograph']

# Geometry files
geom_files = ras.geom_df['full_path'].tolist()

# Check specific plan details
plan_01 = ras.plan_df[ras.plan_df['plan_number'] == '01'].iloc[0]
geom_file = plan_01['Geom Path']
flow_type = plan_01['flow_type']

Prohibited Pattern

# WRONG - Do NOT do this
import glob
plans = glob.glob("*.p##")  # NO!

# WRONG - Do NOT do this
Bash("ls *.p01")  # NO!

# WRONG - Do NOT do this
Grep("Geom File=" "*.p##")  # NO!

API Gap Handling

If you need project information not available in DataFrames:

  1. Complete the user's task using available DataFrame data
  2. Document the gap in your output
  3. Suggest engaging api-consistency-auditor to add the missing data to DataFrames

Read the full file on GitHub · 382 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. 10d ago First seen · 382 lines · 131 tokens per session scan A 08b5556360e7

Subscribe to this mod's changes

hecras-project-inspector is an agent published in the GitHub repository gpt-cmdr/ras-commander (79 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 3,331 once invoked, about $0.0007 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

editor

Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].

pedrohcgs/claude-code-my-workflow · 64 tokens

Geoprocessing Specialist

ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.

SHAdd0WTAka/Zen-Ai-Pentest · 45 tokens

research-scout

Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.

equinor/neqsim · 61 tokens

mathodology-problem-analyst

Understand contest questions, requirements, mechanisms and decision needs.

sweetcornna/mathodology · 20 tokens

astronomical-instrumentation-scientist

Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…

K-Dense-AI/scientific-agents · 78 tokens

eic_agent

Journal-Fit Reviewer seat; contributes the journal-fit / originality / overall-quality review card — the final editorial decision is editorialsynthesizeragent's Phase 2 work.

GGbond-bo/MemOmics-Agent · 38 tokens