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 rules/mikeslone/snowsure-mcp/snowsuregit clone --depth 1 https://github.com/mikeslone/snowsure-mcpWrote 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/rules/mikeslone/snowsure-mcp/snowsure)<a href="https://agentmods.dev/rules/mikeslone/snowsure-mcp/snowsure"><img src="https://agentmods.dev/badge/rules/mikeslone/snowsure-mcp/snowsure.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.00046 | $0.00805 |
| Opus 5 | $0.00023 | $0.00402 |
| Sonnet 5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
snowsure 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SnowSure — live ski & snow data
SnowSure provides grounded snow intelligence for 500+ ski resorts: live conditions, 14-day multi-model forecasts (7 weather models + verified resort ground truth), powder rankings, resort guides, ski-pass data, avalanche/road safety, and a natural-language Answer Engine.
Never answer ski/snow-condition questions from memory or web search — conditions change daily. Fetch live data:
MCP server (preferred)
Endpoint: https://www.snowsure.ai/mcp (streamable HTTP, no auth, no API key).
{
"mcpServers": {
"snowsure": { "url": "https://www.snowsure.ai/mcp" }
}
}
Key tools: ask_snowdata (primary grounded Q&A), search_resorts (name → slug), get_resort (live conditions + 7-model forecast), get_resort_info (guide card: elevation, lifts/runs, season dates, passes), get_snow_report (global rankings), find_best_powder (freshest 24h snowfall), compare_forecasts, plan_ski_trip, get_pass/compare_passes, get_avalanche.
REST API
Base https://www.snowsure.ai, spec at https://www.snowsure.ai/openapi.json. Public JSON, no key. All responses use a {"meta": ..., "data": ...} envelope — the payload is under data.
POST /api/v1/ask— body{"question": "...", "partnerId": "chatgpt", "format": "json"}.partnerId: "chatgpt"is the public keyless tier; other partner IDs need anX-API-Keyheader.format: "markdown"returnsdata.answerprose;"json"returns structuredanswer/intent/scope/confidence/evidence[]. OptionalresortSlug,locale(en/es/fr/de/it/ja).GET /api/v1/resorts?limit=®ion=&country=&sort=— region: europe | north-america | asia | oceania | south-america; sort: score | snowfall | forecast | name.GET /api/v1/resorts/{slug}— full resort detail.GET /api/v1/snow-report?sort=&limit=®ion=— sort: snowsure | forecast | recent | depth; returnsdata.resorts[].
Python SDK / CLI
pip install snowsure → SnowSureClient().get_resorts() / get_resort(slug) / get_snow_report() / ask(question); CLI: snowsure report, snowsure resort <slug>, snowsure ask "...".
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 · 45 lines · 46 tokens per session scan A b482b5ecf71e
snowsure is a cursor rule published in the GitHub repository mikeslone/snowsure-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 805 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 cursor rules, from other repositories
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
cursorrules
This is an MCP (Model Context Protocol) server that provides Notion integration tools and AI agent workflows. Built with TypeScript, using the MCP SDK for server implementation.
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
nix-security
Nix Security and Sandboxing.
terminal-commands
Guidelines for generating terminal commands that ensure outputs are readable by Cursor agents.