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 runxhq/runx --skill nws-weather-forecastgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/nws-weather-forecast)<a href="https://agentmods.dev/skills/runxhq/runx/nws-weather-forecast"><img src="https://agentmods.dev/badge/skills/runxhq/runx/nws-weather-forecast/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/runxhq/runx/nws-weather-forecast"><img src="https://agentmods.dev/badge/skills/runxhq/runx/nws-weather-forecast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.01068 |
| Opus 5 | $0.00014 | $0.00534 |
| Sonnet 5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
nws-weather-forecast 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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NWS Weather Forecast
Fetch public National Weather Service forecast evidence through runx HTTP.
This is a branded provider skill for the canonical weather-forecast verb. It
uses the governed HTTP front, not an ad hoc client: the receipt records the NWS
endpoint, response status, graph step receipts, and the exact authority surface.
No API key is required. The default runner fetches the actual NWS gridpoint
forecast; the locate runner discovers the gridpoint for a latitude/longitude.
What this skill does
nws-weather-forecast makes read-only calls to api.weather.gov. The locate
runner calls /points/{lat},{lon} to discover gridId, gridX, gridY, and
forecast URLs. The default forecast runner calls
/gridpoints/{office}/{grid_x},{grid_y}/forecast to fetch forecast periods. The
output is provider evidence; use weather-forecast when an agent needs to
normalize that evidence for a planning decision.
When to use this skill
- You need real public weather evidence with no credentials.
- A graph needs to prove a weather data read went through runx's governed HTTP path.
- You have an NWS office/gridpoint and need the current public forecast.
- You have latitude and longitude in the United States and need the NWS gridpoint before running the forecast path.
When not to use this skill
- For locations outside NWS coverage. Return
needs_inputwith the coverage limitation. - For emergency, medical, aviation, maritime, evacuation, or life-safety decisions.
- To notify users, reschedule events, deploy changes, or mutate operations based on weather. Those actions need their own authority gate.
- To call private networks, untrusted hosts, or non-NWS endpoints.
Procedure
- If the caller has only coordinates, run
locatewithlatandlon. - Extract
gridId,gridX, andgridYfrom the sealed locate output. - Run the default
forecastrunner withoffice,grid_x, andgrid_y. - Confirm the HTTP status is 2xx and the response contains forecast periods.
- Preserve the NWS source URL, generated timestamp, gridpoint, and receipt refs.
- If an agent needs planning prose, pass the provider evidence to
weather-forecast. Do not invent guidance inside this provider fetch. - Return
needs_inputfor malformed coordinates or gridpoints; returnneeds_more_evidencefor NWS outages, missing periods, or stale data.
What ships with it
3 files 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.
- 8d ago First seen · 109 lines · 28 tokens per session scan A 382cdef84f66
nws-weather-forecast is a skill published in the GitHub repository runxhq/runx (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,068 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.