Borrowing it
Nothing to install: this file belongs to lostnumber07/shearline. 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/lostnumber07/shearline/main/.claude/skills/hail-claim-verification/SKILL.mdgit clone --depth 1 https://github.com/lostnumber07/shearlineWrote 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/lostnumber07/shearline/hail-claim-verification)<a href="https://agentmods.dev/skills/lostnumber07/shearline/hail-claim-verification"><img src="https://agentmods.dev/badge/skills/lostnumber07/shearline/hail-claim-verification/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/lostnumber07/shearline/hail-claim-verification"><img src="https://agentmods.dev/badge/skills/lostnumber07/shearline/hail-claim-verification.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.00059 | $0.00808 |
| Opus 5 | $0.00030 | $0.00404 |
| Sonnet 5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
hail-claim-verification 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hail-claim verification
Goal: produce a defensible corroborated / partially corroborated / not corroborated verdict for a hail claim at a specific location and date, with the evidence and its distance/time from the claimed loss.
Reminder: SHEARLINE data is informational and preliminary (NWS/spotter reports), not a legal adjudication or the final NCEI Storm Events record. State that in the output.
Inputs you need
- Location — a street address or place. Geocode it to
lat, lon(decimal degrees, CONUS only; longitude is negative in the US). - Date of the alleged hail — a single UTC calendar day,
YYYY-MM-DD. If the claimant gives a local date/time near midnight, check the adjacent UTC day too. - Claimed hail size (optional, inches) — to compare against reports.
Procedure
-
Pull ground-truth reports for that day.
get_historical_storm_reports(lat, lon, date, radius_km=40)- Read
data.counts.hailand thedata.reportsentries withcategory: "hail". - For each hail report note
magnitude(inches),time_utc, anddistance_km/directionfrom the claim location.
- Read
-
If the event was within the last ~24 hours, add radar-derived hail.
get_mrms_severe(lat, lon, radius_km=40)data.hail_mesh.max_mesh_inis the radar Maximum Estimated Size of Hail in the last hour, with the distance/bearing of the maximum. (MRMS only retains ~24–48 h, so this step applies to recent claims only; for older dates rely on step 1.)
-
Widen if nothing close. If no hail report is within ~15 km, re-run step 1 with
radius_km=80to see whether a hail swath passed nearby (hail is highly localized; a report 30 km away is weak support). -
Form the verdict.
- Corroborated — a hail report (or MESH ≥ 1") within ~15 km and within a few hours of the claimed time, of comparable or larger size.
- Partially corroborated — hail reported in the broader area (15–40 km) or of smaller size than claimed.
- Not corroborated — no hail reports within 40 km on that UTC day (note that pre-2005 dates aren't covered, and an empty old-date result is not proof of a quiet day).
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 · 62 lines · 59 tokens per session scan A 1c2a571daa3a
hail-claim-verification is a skill published in the GitHub repository lostnumber07/shearline (0 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 808 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-31.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
agreement-setup
Set up a bKash tokenized agreement for repeat charges and check its status.
planfix-api
A Planfix CRM integration for managing tasks and contacts. A CRM is a system for organizing customer and business relationships.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).