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 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/weather-forecast)<a href="https://agentmods.dev/skills/runxhq/runx/weather-forecast"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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/weather-forecast"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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.00052 | $0.00563 |
| Opus 5 | $0.00026 | $0.00282 |
| Sonnet 5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weather Forecast
Interpret supplied weather evidence, then let the deterministic finalizer bind the result to that evidence.
This skill is read-only. It does not fetch forecasts, send alerts, change schedules, or mutate provider state. Use nws-weather-forecast, open-meteo-weather-forecast, or another provider skill to obtain evidence first.
Procedure
- Identify the requested location, horizon, purpose, and freshness requirement.
- Read only
forecast_evidence. Do not add provider references, timestamps, or forecast periods that are absent from it. - Assess whether the evidence is fresh and complete enough for the stated purpose. Return
needs_more_evidencewhen it is stale, ambiguous, unsupported, or too thin. - Summarize relevant periods, uncertainty, hazards, and planning implications without claiming a downstream action occurred.
- Return
refusedfor emergency, evacuation, aviation, maritime, medical, or other life-safety use.
The finalizer enforces the requested location and horizon, context-only authority, provider identity, provenance references, generation timestamp, and period-name fidelity. A draft that invents any of those fails instead of sealing a forecast packet.
Output
decision: ready | needs_input | needs_more_evidence | refused
location: string
horizon: string
forecast_packet:
summary: string
periods: array
hazards: array
confidence: string
generated_at: string
provider_evidence:
provider: string
source_refs: array
receipt_refs: array
safety_notes: array
stop_conditions: array
receipt_notes:
authority: context-only
mutation: false
For ready, the supplied evidence must include provider, generated_at, periods, and at least one source_ref or receipt_ref. Missing forecast_evidence stops before agent interpretation. A missing optional horizon remains an empty string; the agent must not invent one.
Agent task contracts
weather-forecast-interpret
Interpret only the supplied forecast evidence and return forecast_draft using the documented output fields. Preserve the requested location and horizon, provider, generated_at, source_refs, receipt_refs, and relevant period names. Summaries, hazards, uncertainty, and stop conditions require analyst judgment, but do not invent evidence. Return needs_more_evidence when freshness or coverage is insufficient. Return refused for life-safety use.
What ships with it
6 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.
- 9d ago First seen · 56 lines · 52 tokens per session scan A b1828f418780
weather-forecast is a skill published in the GitHub repository runxhq/runx (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 52 tokens to every session and 563 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-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.