What is event-day-lightning-watch?

An event safety procedure for monitoring lightning near a fixed outdoor venue. It uses weather threat checks and distance-based rules to recommend continuing, suspending, sheltering, or resuming activities.

Use it for stadiums, festivals, golf, drone operations, construction, or other outdoor events in the continental United States, with the venue location, event times, and polling interval.

It gives a safety officer consistent decision points while lightning conditions change during an event.

How lostnumber07/shearline configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/lostnumber07/shearline/main/.claude/skills/event-day-lightning-watch/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lostnumber07/shearline

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lostnumber07/shearline/event-day-lightning-watch/github.svg)](https://agentmods.dev/skills/lostnumber07/shearline/event-day-lightning-watch)

Your own site

<a href="https://agentmods.dev/skills/lostnumber07/shearline/event-day-lightning-watch"><img src="https://agentmods.dev/badge/skills/lostnumber07/shearline/event-day-lightning-watch/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lostnumber07/shearline/event-day-lightning-watch"><img src="https://agentmods.dev/badge/skills/lostnumber07/shearline/event-day-lightning-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 683 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.

Model	Per session	Once invoked
Fable 5.1	$0.00075	$0.00683
Opus 5.5	$0.00030	$0.00273
Sonnet 5.5	$0.00015	$0.00137
Haiku 4.5	$0.00007	$0.00068

Measured 2mo ago against content hash ce9a42fba5f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

event-day-lightning-watch 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 2mo 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/skills/event-day-lightning-watch/SKILL.md · 56 lines

How it starts

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

Event-day lightning watch

Goal: keep people safe at a fixed outdoor venue by polling lightning proximity and issuing clear continue / suspend / shelter / resume calls using standard lightning-safety thresholds.

Reminder: this supports an on-site safety officer; it does not replace one. The venue's emergency plan and official warnings take precedence.

Inputs you need

Venue — lat, lon (CONUS).
Event window — start/end local time.
Poll interval — every 5–10 minutes during the window (lightning evolves fast).

Standard thresholds (apply these consistently)

≤ 10 km from the venue → SHELTER NOW (strikes essentially overhead; 30-30 rule).
≤ 16 km (~10 mi) → SUSPEND outdoor activity, move toward shelter.
> 16 km but present / approaching → HEIGHTENED WATCH, ready to suspend.
Resume only 30 minutes after the last strike within 16 km.

Procedure

Pre-event baseline. get_threat_brief(lat, lon)
- Note the overall threat_level, the attention_window, and any lightning_summary. If the brief is already elevated+ for storms/lightning, brief the safety officer before doors open.
Poll during the event. Every 5–10 min: get_lightning(lat, lon, radius_km=16, minutes=15)
- Read data.flash_count, data.flashes_per_min, and data.nearest_strike.distance_km / time_utc.
- Apply the thresholds above to set the current call.
- Track the last strike time within 16 km to drive the 30-minute resume clock.
Escalation check. If lightning appears or the flash rate climbs, also run get_threat_brief(lat, lon) to see whether severe weather (not just lightning) is developing — hail/wind/tornado may warrant evacuation beyond a lightning hold.
Resume. When get_lightning shows no strikes within 16 km for a continuous 30 minutes, clear the suspension.

Output template (per poll)

[<time_utc>] Lightning watch — <venue>
Nearest strike: <dist> km <dir> at <time_utc>  (flashes <n>, <rate>/min within 16 km)
CALL: <CONTINUE | HEIGHTENED WATCH | SUSPEND | SHELTER NOW | CLEARED>
Resume eligible at: <last-strike-time + 30 min, or "n/a">
Notes: <e.g. "rate increasing, cell approaching from SW">

Read the full file on GitHub · 56 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.

2mo ago First seen · 56 lines · 75 tokens per session scan A ce9a42fba5f0

Subscribe to this mod's changes

event-day-lightning-watch is a skill published in the GitHub repository lostnumber07/shearline (1 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 683 once invoked, about $0.0003 per session on Opus 5.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.

Scientific

event-day-lightning-watch next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
event-day-lightning-watchlostnumber07/shearline	Skill	1	1mo ago	MIT	A	75	Claude Code
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	2d ago	Apache-2.0	A	123	Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	83	Claude Code
matlabK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	44	Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skills	Skill	56k	4d ago	MIT	A	71	Claude Code, Codex
research-engineerdavila7/claude-code-templates	Skill	33k	yesterday	MIT	A	43	Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmed	Skill	5.8k	yesterday	Apache-2.0	A	205	Claude Code

shearline: Skill for Claude Code