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-onboardinggit 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-onboarding)<a href="https://agentmods.dev/skills/smarterweather/developer/smarterweather-onboarding"><img src="https://agentmods.dev/badge/skills/smarterweather/developer/smarterweather-onboarding/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-onboarding"><img src="https://agentmods.dev/badge/skills/smarterweather/developer/smarterweather-onboarding.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.00077 | $0.00891 |
| Opus 5.5 | $0.00031 | $0.00356 |
| Sonnet 5.5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
smarterweather-onboarding 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard to Smarter Weather (one-shot)
This install is temporary. It talks to the onboarding MCP at
https://mcp.developers.smarterweather.com. After a key exists and the
weather client is configured, remove this server from the client
config. Never wire it into a long-lived config alongside the weather MCP
(https://mcp.smarterweather.com).
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. Tell the user before signup if they need weather elsewhere. 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 lists that cover the whole country, are not filtered by point, so do not treat an empty result as an all-clear.
Flow
Prefer CLI when possible:
npx -y @smarterweather/mcp-onboarding@latest login # human present
npx -y @smarterweather/mcp-onboarding@latest trial # no human
Both write .env and print only a key prefix. Otherwise:
- Connect with no credentials. Call
get_plans/get_documentation/sign_up. sign_upreturns a Clerk signup URL. A human opens it and creates a free account (no credit card).- Reconnect this MCP with OAuth when the host prompts. The stdio bridge
(
npx -y @smarterweather/mcp-onboarding) uses a loopback callback on port3334— keep that port free. Cursor's nativecursor://OAuth against Clerk is broken; prefer the stdio bridge for gated tools. - Call
create_api_key(idempotent). Via the stdio bridge the key is written to.envand not returned. Prefer CLIloginwhen a human can approve a device code. - Call
configure_mcp. Cursor getsenvFile: ${workspaceFolder}/.env; Claude Desktop getsSMARTERWEATHER_ENV_FILEpointing at the project.env(a path, never the key). Never pastesw_live_/sw_test_into committed JSON. - Install the weather plugin or
@smarterweather/mcp-weather, then remove this onboarding server.
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 b731621229d4
- 13d ago Changed · +16 lines adaacf115fb5
- 1mo ago Changed · +10 lines f732e3c1f8b9
- 1mo ago First seen · 50 lines · 77 tokens per session scan A ced25b71fe70
smarterweather-onboarding is a skill published in the GitHub repository smarterweather/developer (1 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 891 once invoked, about $0.0003 per session on Opus 5.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.
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…
headless-step-provision-webapp
Provision a plain Node.js app host for the Hostinger Headless flow: create an empty website (no WordPress, no store engine, no /cms), optionally a MySQL database, then record it in site.json. For any webapp / SPA / app that brings its own code and data.
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.