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.
npx skills add OpenLAIR/OpenSkill --skill evo-flood-risk-analysisgit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/skills/openlair/openskill/evo-flood-risk-analysis)<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.
<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>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.00060 | $0.00643 |
| Opus 5 | $0.00030 | $0.00321 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
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.
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']) 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
- Gage height (parameter 00065) is used — NOT discharge (00060).
- 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(). - 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_idorgaugelidcolumn). The flood stage column issigstages.flood.stageor similar. - Flood condition:
daily_max_gage_height >= flood_stage(greater than or equal). - Only stations with a valid numeric NWS flood stage are evaluated.
- Only stations with at least one flood day are included in output.
- Sort output by
flood_daysdescending.
Key Technical Rules
- Preserve leading zeros: USGS station IDs are 8–15 digit strings (e.g.,
04031000). Always read/store as strings. - Parameter codes:
00065= gage height (ft). Use instantaneous values (get_iv), NOT daily values (get_dv). - Missing data: Use
pd.to_numeric(errors='coerce')to handle non-numeric sensor flags. - Tuple unpacking:
nwis.get_iv()returns(DataFrame, Metadata)— always unpack. - API rate limiting: Use brief
time.sleep(0.5)between station requests. - 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'
)
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.
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.
- yesterday First seen · 48 lines · 60 tokens per session scan A 62674a67a0d3
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.
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.
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.
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.
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.
statistical-theory-analysis
Analyze theoretical properties of statistical methods under the formal formulation: identifiability, bias, variance, consistency, asymptotics, coverage, error bounds, robustness, and limitations.
meta-analysis
Statistical methods for combining results across multiple studies. Use when aggregating cross-study or cross-experiment results.