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 agentmods add instructions/nanookai/open-meteo-api/agents-mdgit clone --depth 1 https://github.com/NanookAI/open-meteo-apiWrote 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/instructions/nanookai/open-meteo-api/agents-md)<a href="https://agentmods.dev/instructions/nanookai/open-meteo-api/agents-md"><img src="https://agentmods.dev/badge/instructions/nanookai/open-meteo-api/agents-md.svg" alt="Measured on agentmods" 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 | $0.00859 | $0.00859 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
open-meteo-api AGENTS.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(`curl "https://api.open-meteo.com/v1/forecast?..."`) before it goes into the How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repository contains an Agent Skill that teaches AI agents how to use the Open-Meteo weather API (https://open-meteo.com/). The deliverable is documentation, not application code.
Layout
skills/open-meteo-api/SKILL.md— skill entry point (frontmatter, workflow, forecast + geocoding APIs, WMO codes)skills/open-meteo-api/scripts/get_weather.py— zero-dependency CLI covering the common case (place name → current + daily forecast)skills/open-meteo-api/references/weather-variables.md— full current/hourly/daily variable catalog and complete WMO weather code tableskills/open-meteo-api/references/other-apis.md— archive, air quality, marine, elevation, flood, climate, and ensemble APIs
Conventions
- English only in all files. No Chinese or other non-English text in any committed file, including examples and comments.
- Verify before documenting. Every request/response example and every
variable name must be checked against the live API
(
curl "https://api.open-meteo.com/v1/forecast?...") before it goes into the docs. Do not copy variable names or response shapes from memory — the API evolves and invalid variable names fail with HTTP 400. - Keep SKILL.md lean (well under 500 lines). SKILL.md carries the workflow
(geocode → fetch → interpret weather_code) plus the most-used variables;
exhaustive catalogs and secondary endpoints belong in
references/, with a clear pointer from SKILL.md telling the reader when to open them. - Explain the why. When documenting a pitfall or rule, state the reason
(e.g. "daily aggregation without
timezoneuses GMT day boundaries") so agents can generalize instead of pattern-matching. - Free tier is the default stance. Document the keyless non-commercial API. Mention paid/commercial options only in passing, never as a prerequisite.
- The script stays dependency-free.
get_weather.pymust run on a bare Python 3.8+ standard library (urllib, json, argparse) so it works in any agent sandbox without a pip install. It covers only the common case; niche needs are served by documentation, not more script flags.
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.
- 4d ago First seen · 63 lines · 859 tokens per session scan A a01072a19228
open-meteo-api AGENTS.md is an instructions file published in the GitHub repository NanookAI/open-meteo-api (2 stars, last pushed 2mo ago), licensed MIT. It adds 859 tokens to every session, about $0.0043 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
SeekMoney-ai CLAUDE.md
Claude Code instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
sentry-instrumentation AGENTS.md
Instructions for tortastudios/sentry-instrumentation, covering agents guide — sentry-instrumentation, what this repo is, this repo has no "skill registry", if you're a codex agent asked to install this skill and skill-enable block (copy into consumer agents.md).
Cerebro AGENTS.md
Instructions for AgenticFirst/Cerebro, covering cerebro — agent context, read before touching integrations, project layout, conventions a fresh agent would otherwise miss and running locally.
critical-thinking AGENTS.md
Instructions for Johna2an/critical-thinking, covering agents.md, repo map, install (for a user asking "should i install this?"), working in this repo and running an eval round.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
hometax-doum AGENTS.md
AGENTS.md instructions for lbiz-partners/hometax-doum, covering claude.md — hometax-doum 개발 규칙 (하네스와 쌍), 규칙 ↔ 강제 장치 and 운용 메모.