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/skills/ebfe_crawl_s3-catalog/SKILL.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/skills/gpt-cmdr/ras-commander/ebfe_crawl_s3-catalog)<a href="https://agentmods.dev/skills/gpt-cmdr/ras-commander/ebfe_crawl_s3-catalog"><img src="https://agentmods.dev/badge/skills/gpt-cmdr/ras-commander/ebfe_crawl_s3-catalog/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/gpt-cmdr/ras-commander/ebfe_crawl_s3-catalog"><img src="https://agentmods.dev/badge/skills/gpt-cmdr/ras-commander/ebfe_crawl_s3-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 51 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 109 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00058 | $0.01447 |
| Opus 5 | $0.00029 | $0.00724 |
| Sonnet 5 | $0.00012 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
ebfe_crawl_s3-catalog 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 11d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eBFE / BLE S3 Catalog Crawl Skill
Crawl FEMA's public BLE S3 bucket and build a local catalog of available Base Level Engineering datasets. Cache results so repeated sessions don't re-crawl.
When to Use
- "What BLE models are available for [state/watershed]?"
- "Get the eBFE catalog for Texas"
- Before any BLE model download or eBFE workflow
- When
RasCatalog/RasSourcesneeds to be populated
S3 Source
Bucket: s3://fim-public-availability-data/ (FEMA public, no auth required)
Structure:
fim-public-availability-data/
└── ble/
└── {state}/
└── {huc8}/
├── Hydraulics/
│ └── {project}.zip ← HEC-RAS model
├── Terrain/
└── Mapping/
Alternative bucket (check both):
s3://ras2fim-dev/
s3://fim-dev-outputs/
Crawl Workflow
Step 1: Check Local Cache First
from pathlib import Path
import json
cache_path = Path(".claude/outputs/ble-catalog-cache.json")
if cache_path.exists():
import time
age_days = (time.time() - cache_path.stat().st_mtime) / 86400
if age_days < 30:
with open(cache_path) as f:
catalog = json.load(f)
print(f"Using cached catalog ({age_days:.0f} days old, {len(catalog)} entries)")
# Skip crawl, use catalog
Step 2: Crawl S3 (if cache miss or stale)
import boto3
from botocore import UNSIGNED
from botocore.config import Config
# Public bucket — no credentials needed
s3 = boto3.client('s3', config=Config(signature_version=UNSIGNED))
bucket = "fim-public-availability-data"
prefix = "ble/"
# Optional: filter by state
state_filter = "TX" # or None for all states
if state_filter:
prefix = f"ble/{state_filter}/"
paginator = s3.get_paginator('list_objects_v2')
catalog = []
for page in paginator.paginate(Bucket=bucket, Prefix=prefix, Delimiter='/'):
for obj in page.get('Contents', []):
key = obj['Key']
size = obj['Size']
# Filter to hydraulics .zip files
if 'Hydraulics' in key and key.endswith('.zip'):
parts = key.split('/')
# parts: ['ble', state, huc8, 'Hydraulics', filename]
if len(parts) >= 5:
catalog.append({
'state': parts[1],
'huc8': parts[2],
'filename': parts[-1],
's3_path': f"s3://{bucket}/{key}",
'size_mb': round(size / 1e6, 1),
})
print(f"Found {len(catalog)} BLE hydraulic models")
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.
- 11d ago First seen · 191 lines · 58 tokens per session scan A e6c3df0f9ab1
ebfe_crawl_s3-catalog is a skill published in the GitHub repository gpt-cmdr/ras-commander (79 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,447 once invoked, about $0.0003 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 skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…