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 smarterweather/developer --skill smarterweather-apigit clone --depth 1 https://github.com/smarterweather/developerWrote 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/smarterweather/developer/smarterweather-api)<a href="https://agentmods.dev/skills/smarterweather/developer/smarterweather-api"><img src="https://agentmods.dev/badge/skills/smarterweather/developer/smarterweather-api/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/smarterweather/developer/smarterweather-api"><img src="https://agentmods.dev/badge/skills/smarterweather/developer/smarterweather-api.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.00120 | $0.03302 |
| Opus 5.5 | $0.00048 | $0.01321 |
| Sonnet 5.5 | $0.00024 | $0.00660 |
| Haiku 4.5 | $0.00012 | $0.00330 |
Grade A, and why
smarterweather-api 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: read only the key, never `source` the file as shell (the last How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use the Smarter Weather REST API
The platform offers two surfaces; pick the right one for the user's goal:
| Goal | Use |
|---|---|
| Code that runs in production and calls weather endpoints from the user's own service | REST API (api.smarterweather.com/v1/*) — this skill |
| An AI agent that calls weather tools live during a chat session | MCP servers — see the smarterweather-mcp skill |
| One-time onboarding (account, key minting, client config) | @smarterweather/mcp-onboarding MCP — see the smarterweather-mcp skill |
When in doubt, default to REST for code-generation tasks and MCP for agent-runtime tool calls.
Coverage: Smarter Weather covers the 50 US states and DC only. The US territories (Puerto Rico, the US Virgin Islands, Guam, the Northern Mariana Islands and American Samoa) and other countries are outside it. Every route that takes a point (lat and lon, zip or location) returns 404 outside-coverage for a point outside the 50 states and DC. /v1/alerts and /v1/observations return it for a bounding box that touches no US domain (CONUS, Alaska, Hawaii); a box that touches one may still include area outside the US. /v1/weather/batch reports it per item as outside_coverage, and /v1/point with points and /v1/series/batch mark such points out_of_domain, as they do a point the check could not reach in time (retry it). If the location lookup is unavailable, the check can briefly fail open. Routes keyed by a station, radar site, forecast office or alert id, and nationwide lists, are not filtered by point, so do not treat an empty result as an all-clear. Do not retry an outside-coverage response.
Authentication — required reading
Every Smarter Weather request is authenticated with an API key. Never
hard-code keys. Keep the key in the project's .env (mode 0600,
gitignored) and read it from the environment in server-side code:
# .env -- written for you by `login` / `trial` below
SMARTERWEATHER_API_KEY=sw_live_...
Load it before the samples below run:
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 Changed · +42 lines · -17 tokens per session 9adcc2c3fb09
- 8d ago Changed · +39 lines 35cbbd41e669
- 1mo ago Changed · +4 lines 50824f0d318f
- 1mo ago First seen · 193 lines · 137 tokens per session scan A ee38f281b110
smarterweather-api is a skill published in the GitHub repository smarterweather/developer (1 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 3,302 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
API Rate Limiting Testing
Testing API rate limiting implementations including throttling behavior, burst handling, rate limit headers, and distributed rate limiting patterns.
API Versioning Testing
Testing API versioning strategies including URL path, header, and query parameter versioning with backward compatibility validation.
Contract-First Testing
Contract-first testing approach using Pact, Spring Cloud Contract, or Dredd for ensuring API consumer-provider compatibility.
headless-step-provision-wordpress
Provision a headless WordPress backend for the Hostinger Headless flow: create the headless website with WordPress at /cms, verify and self-heal, then record it in site.json.
headless-step-content-model
Step 4 (content model) of the Hostinger Headless flow. Prepare phase: turns brief.md into a content helper (content-model.md) — fixed Title/Description plus a tailored generation prompt per section (Navigation, Pages, Articles) — and generates the drafts/images, no live backend needed. Push phase: routes to the…