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 skills/smarterweather/developer/use-smarterweather-apinpx skills add smarterweather/developer --skill use-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/use-smarterweather-api)<a href="https://agentmods.dev/skills/smarterweather/developer/use-smarterweather-api"><img src="https://agentmods.dev/badge/skills/smarterweather/developer/use-smarterweather-api.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.1 | $0.00031 | $0.00263 |
| Opus 5 | $0.00015 | $0.00131 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
use-smarterweather-api 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 5d 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
Use the Smarter Weather developer platform
This path is a stub. The canonical playbooks live in the smarterweather
Agent Plugin:
- REST API:
plugins/smarterweather/skills/smarterweather-api/SKILL.md - Hosted MCP:
plugins/smarterweather/skills/smarterweather-mcp/SKILL.md
Hosted copies (same prose, authored in the private monorepo and published on the developer portal):
- https://developers.smarterweather.com/.well-known/skills/smarterweather-api/SKILL.md
- https://developers.smarterweather.com/.well-known/skills/smarterweather-mcp/SKILL.md
Install the plugin from plugins/smarterweather/ (Cursor Marketplace
source: .cursor-plugin/marketplace.json). Do not use the stale
Phase-preview copy that used to live here.
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.
- 5d ago First seen · 25 lines · 31 tokens per session scan A 780e1406a756
use-smarterweather-api is a skill published in the GitHub repository smarterweather/developer (1 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 263 once invoked, about $0.0002 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
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.
weather
Get current weather and forecasts.
API Fuzzing
API endpoint fuzzing for discovering unexpected behaviors, crashes, and security vulnerabilities through malformed requests, boundary values, and protocol violations.
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.