Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/ivancampos/agents/open-meteo-weather)<a href="https://agentmods.dev/skills/ivancampos/agents/open-meteo-weather"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/open-meteo-weather/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/ivancampos/agents/open-meteo-weather"><img src="https://agentmods.dev/badge/skills/ivancampos/agents/open-meteo-weather.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.00079 | $0.00495 |
| Opus 5 | $0.00039 | $0.00247 |
| Sonnet 5 | $0.00016 | $0.00099 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
open-meteo-weather 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 12d 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.
What it actually says
Open-Meteo Weather
Overview
Fetch current weather from Open-Meteo with a tiny, deterministic flow. Prefer the script for repeatable calls; fall back to raw URL construction when asked for a direct API call.
Quick Start
- Use the script for location names:
/Users/ivancampos/.codex/skills/open-meteo-weather/scripts/open_meteo_current.py --location "Boston, MA"
- Use the script for explicit coordinates:
/Users/ivancampos/.codex/skills/open-meteo-weather/scripts/open_meteo_current.py --lat 42.3601 --lon -71.0589
- Provide a direct API call when the user requests a raw URL:
https://api.open-meteo.com/v1/forecast?latitude=42.3601&longitude=-71.0589¤t_weather=true&timezone=auto
Workflow
- Determine input type: location name or lat/lon.
- If location name is provided, geocode first (use the Open-Meteo geocoding API).
- Call the forecast endpoint with
current_weather=trueandtimezone=auto. - Return JSON with
locationand a normalizedcurrent_weatherobject.- Include both
temperature_candtemperature_f. - Use keys:
windspeed_kmh,winddirection_deg,weathercode,is_day,time,interval.
- Include both
Examples
- “Get current weather in Boston” → geocode, then call forecast.
- “Use this URL for Medford, MA” → provide direct forecast URL with given lat/lon.
Resources
scripts/
open_meteo_current.py: CLI for location or lat/lon; prints JSON withlocationandcurrent_weather.
references/
open_meteo.md: endpoint and parameter quick reference.
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.
- 12d ago First seen · 48 lines · 79 tokens per session scan A 53f622e4e127
open-meteo-weather is a skill published in the GitHub repository IvanCampos/agents (5 stars, last pushed 7mo ago), licensed MIT. It adds 79 tokens to every session and 495 once invoked, about $0.0004 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
skill-authoring
Author SKILL.md: frontmatter, structure, writing principles.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
academic-paper-review
Structured peer-review of academic papers.