developer AGENTS.md

A set of instructions for connecting software agents to Smarter Weather, a weather data service. It covers the service’s REST API and MCP connections, authentication, sign-up, and documentation.

In plain words
What is it for?
Use it to discover the weather service, create an account and API key, configure a connection, and work with its REST API or weather tools.
Why use it?
It gives an agent the correct path through account setup, API keys, authentication, and error handling instead of leaving those details to guesswork.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/smarterweather/developer/agents-md
Clone the repo
git clone --depth 1 https://github.com/smarterweather/developer

Made for: Codex, OpenCode.

Per session 686 This file is loaded in full into every session.
When invoked 686 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00686 $0.00686
Opus 5 $0.00343 $0.00343
Sonnet 5 $0.00137 $0.00137
Haiku 4.5 $0.00069 $0.00069

Measured yesterday against content hash 769ceef02696, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

developer AGENTS.md 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 yesterday.

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.

AGENTS.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — Smarter Weather developer platform

Guidance for AI agents integrating with Smarter Weather.

Surfaces

Surface Endpoint Auth
REST API https://api.smarterweather.com Authorization: Bearer sw_live_* / sw_test_*
Weather MCP https://mcp.smarterweather.com OAuth 2.1 + PKCE, or API key Bearer
Onboarding MCP https://mcp.developers.smarterweather.com Anonymous discovery tools; OAuth for account tools

Canonical machine-readable contracts:

Preferred onboarding path

  1. Connect to the onboarding MCP with no credentials.
  2. Call get_plans / get_documentation / sign_up. sign_up returns a Clerk signup URL; a human completes account creation in the browser (no credit card for the free tier).
  3. Complete Clerk OAuth when the host prompts.
  4. Call create_api_key (idempotent) and configure_mcp.
  5. Use the returned key against the weather MCP or REST API.

stdio bridges (local clients that cannot speak Streamable HTTP):

npx -y @smarterweather/mcp-onboarding
npx -y @smarterweather/mcp-weather

Do not append @previewlatest is the GA bridge. Set SMARTERWEATHER_API_KEY in the process environment for headless weather calls; set SMARTERWEATHER_ONBOARDING_AUTH=required to force onboarding OAuth for account-scoped tools. Authenticated onboarding uses a pre-registered public PKCE Clerk client (DCR off); ensure port 3334 is free for the loopback callback. Prefer the stdio bridge over Cursor's native url OAuth for gated tools (Clerk + cursor:// is broken).

Auth and errors

  • Prefer Authorization: Bearer <key> (not X-API-Key).
  • Rate-limit headers follow the RateLimit-* family (see docs).
  • Errors use RFC 7807 problem details.

Read the full file on GitHub · 67 lines

Changes

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.

  1. yesterday First seen · 67 lines · 686 tokens per session scan A 769ceef02696

Subscribe to this mod's changes

developer AGENTS.md is an instructions file published in the GitHub repository smarterweather/developer (1 stars, last pushed 5d ago), licensed MIT. It adds 686 tokens to every session, about $0.0034 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.

Related

Other instructions, from other repositories