evo-flood-risk-analysis

evo-flood-risk-analysis is a skill for Claude Code, Codex from OpenLAIR/OpenSkill. It costs 60 tokens per session (643 once invoked), scanned A, original, Apache-2.0.

A flood-analysis pipeline that uses water-level readings from USGS streamgages and official National Weather Service flood-stage thresholds. It summarizes 15-minute gage-height readings into daily maximums and identifies stations and days at or above flood stage.

In plain words
What is it for?
Use it to find flood days across USGS stations and write a sorted CSV listing stations with at least one qualifying day.
Why use it?
It removes the manual work of downloading station data, matching station identifiers, and comparing readings with flood thresholds. It also preserves station IDs correctly, including leading zeros.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find flood days across USGS stations and write a sorted CSV listing stations with at least one qualifying day.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openlair/openskill/evo-flood-risk-analysis
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 OpenLAIR/OpenSkill --skill evo-flood-risk-analysis
Clone the repo
git clone --depth 1 https://github.com/OpenLAIR/OpenSkill

Made for: Claude Code, Codex.

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 evo-flood-risk-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/openlair/openskill/evo-flood-risk-analysis/github.svg)](https://agentmods.dev/skills/openlair/openskill/evo-flood-risk-analysis)
Your own site
<a href="https://agentmods.dev/skills/openlair/openskill/evo-flood-risk-analysis"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-flood-risk-analysis/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 evo-flood-risk-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/openlair/openskill/evo-flood-risk-analysis"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-flood-risk-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00060 $0.00643
Opus 5 $0.00030 $0.00321
Sonnet 5 $0.00012 $0.00129
Haiku 4.5 $0.00006 $0.00064

Measured yesterday against content hash 62674a67a0d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

evo-flood-risk-analysis scanned grade A with 1 finding 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 yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/utils.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

subprocess.check_call([sys.executable, '-m', 'pip', 'install', 'dataretrieval', '-q'])
tasks-evolved/flood-risk-analysis/environment/skills/evo-flood-risk-analysis/SKILL.md · 48 lines

How it starts

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

evo-flood-risk-analysis

End-to-end pipeline for identifying flood days at USGS streamgages using gage height data and NWS flood stage thresholds.

Methodology

  1. Gage height (parameter 00065) is used — NOT discharge (00060).
  2. Daily maximum of instantaneous (15-min) readings is the aggregation method. Use nwis.get_iv() to fetch instantaneous values, then resample to daily max with .resample('D').max().
  3. NWS flood stage thresholds come from the NWS All Gauges Report CSV at https://water.noaa.gov/resources/downloads/reports/nwps_all_gauges_report.csv. Match stations by USGS site ID (usgs_id or gaugelid column). The flood stage column is sigstages.flood.stage or similar.
  4. Flood condition: daily_max_gage_height >= flood_stage (greater than or equal).
  5. Only stations with a valid numeric NWS flood stage are evaluated.
  6. Only stations with at least one flood day are included in output.
  7. Sort output by flood_days descending.

Key Technical Rules

  1. Preserve leading zeros: USGS station IDs are 8–15 digit strings (e.g., 04031000). Always read/store as strings.
  2. Parameter codes: 00065 = gage height (ft). Use instantaneous values (get_iv), NOT daily values (get_dv).
  3. Missing data: Use pd.to_numeric(errors='coerce') to handle non-numeric sensor flags.
  4. Tuple unpacking: nwis.get_iv() returns (DataFrame, Metadata) — always unpack.
  5. API rate limiting: Use brief time.sleep(0.5) between station requests.
  6. No fallback: Do NOT use discharge-based methods. Only gage height vs NWS flood stage.

Usage

import subprocess, sys
subprocess.check_call([sys.executable, '-m', 'pip', 'install', 'dataretrieval', '-q'])

sys.path.insert(0, '/app/environment/skills/evo-flood-risk-analysis/scripts')
from utils import run_flood_analysis

run_flood_analysis(
    stations_file='/root/data/michigan_stations.txt',
    out_file='/root/output/flood_results.csv',
    start='2025-04-01',
    end='2025-04-07'
)

Read the full file on GitHub · 48 lines

Files

What ships with it

1 file 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. yesterday First seen · 48 lines · 60 tokens per session scan A 62674a67a0d3

Subscribe to this mod's changes

evo-flood-risk-analysis is a skill published in the GitHub repository OpenLAIR/OpenSkill (90 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 643 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.

Related

Other skills, from other repositories

fba-simulator

Run Flux Balance Analysis (FBA) and related constraint-based simulations using COBRApy. Covers standard FBA, parsimonious FBA (pFBA), Flux Variability Analysis (FVA), loopless FBA, gene/reaction knockouts, and carbon source swapping. Outputs flux distributions and CSV files.

aiming-lab/AutoResearchClaw · 69 tokens

gsmm-validator

Validate a COBRApy genome-scale metabolic model for mass/charge balance, stoichiometric consistency, biomass producibility, dead-end metabolites, thermodynamic loops, and GPR rule formatting. Outputs a structured validation report with errors and warnings.

aiming-lab/AutoResearchClaw · 52 tokens

gsmm-builder

Build or load a genome-scale metabolic model (GSMM) using COBRApy. Covers loading from BIGG, constructing minimal models from scratch, setting medium constraints, and exporting validated .json model files.

aiming-lab/AutoResearchClaw · 45 tokens

stat-result-validator

Validate statistical research outputs for formulation quality, method-to- problem alignment, theory presence, experimental evidence, fair comparison, artifact completeness, and final-claim consistency.

aiming-lab/AutoResearchClaw · 36 tokens

statistical-theory-analysis

Analyze theoretical properties of statistical methods under the formal formulation: identifiability, bias, variance, consistency, asymptotics, coverage, error bounds, robustness, and limitations.

aiming-lab/AutoResearchClaw · 41 tokens

meta-analysis

Statistical methods for combining results across multiple studies. Use when aggregating cross-study or cross-experiment results.

aiming-lab/AutoResearchClaw · 25 tokens