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 instructions/byteoverdev/peak-window-mcp-app/claude-mdgit clone --depth 1 https://github.com/ByteOverDev/peak-window-mcp-appWhat 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.04256 | $0.04256 |
| Opus 5 | $0.02128 | $0.02128 |
| Sonnet 5 | $0.00851 | $0.00851 |
| Haiku 4.5 | $0.00426 | $0.00426 |
Grade A, and why
peak-window-mcp-app CLAUDE.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 3d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weather MCP Project
Forecast Provider Architecture
PeakWindow uses a multi-provider abstraction (src/providers/) to select the best forecast source for each location. Providers are tried in priority order; on API failure, the router falls through to the next.
| Priority | Provider | Resolution | Coverage | Source |
|---|---|---|---|---|
| 1 | GeoSphere Austria | 2.5 km | Austria & Eastern Alps (9.5–22.1°E, 43–51.8°N) | Direct API (dataset.api.hub.geosphere.at) |
| 2 | MeteoSwiss ICON-CH2 | 2 km | Alpine region (0.5–16.5°E, 43–49.9°N) | Open-Meteo (models=meteoswiss_icon_ch2) |
| 3 | Météo-France AROME | 2.5 km | France & surrounds (-9–14°E, 38–55°N) | Open-Meteo (models=meteofrance_arome_france) |
| 4 | Open-Meteo default | ~11 km | Global | Open-Meteo (best available model blend) |
GeoSphere routing note: the AROME model's true domain reaches west to 5.5°E (BBOX in
geosphere.ts), but its skill is Austria-centric and degrades toward the western edge. So covers()
only makes it the first choice east of 9.5°E (PREFERRED_WEST, ~the Austria–Switzerland border).
West of that — the Swiss/French/Italian Alps, e.g. Matterhorn (7.66°E), Mont Blanc (6.87°E) — the
router falls through to the region-tuned MeteoSwiss ICON-CH2 / Météo-France AROME, which match
Mountain-Forecast notably better on summit temperature and snow line.
Key files:
src/providers/types.ts—ForecastProviderinterface,ForecastProviderResultsrc/providers/geosphere.ts— direct GeoSphere API (deaccumulates precip, derives model terrain fromsp)src/providers/openmeteo.ts— factory for Open-Meteo-based providers (MeteoSwiss, Météo-France, default)src/providers/index.ts— router with ordered fallback
Elevation correction (pressure-level profile + lapse fallback)
Summit temperature is corrected from the forecast grid-cell elevation to the real summit
elevation in analyzeForecast (src/analyze.ts), via two strategies decided per hour in
interpolateAtElevation (src/profile-interp.ts):
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.
- 3d ago First seen · 259 lines · 4,256 tokens per session scan A 671271ffb1bf
peak-window-mcp-app CLAUDE.md is an instructions file published in the GitHub repository ByteOverDev/peak-window-mcp-app (3 stars, last pushed 3mo ago), licensed MIT. It adds 4,256 tokens to every session, about $0.0213 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 instructions, from other repositories
beads-viz AGENTS.md
AGENTS.md instructions for pyros-projects/beads-viz, covering agent instructions — beads viz, quick start, claude desktop configuration, architecture and project structure.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
rag-code-mcp copilot-instructions.md
Instructions for doITmagic/rag-code-mcp, covering copilot instructions - ragcode mcp, ⚖️ the golden rule, project overview, architecture & patterns and developer workflows.
powerbi-mcp CLAUDE.md
Instructions for sulaiman013/powerbi-mcp, covering claude.md and developer notes.
claude-faf-mcp CLAUDE.md
Instructions for Wolfe-Jam/claude-faf-mcp, covering claude.md — claude-faf-mcp, what this is, stack and context.
cosmos-mcp CLAUDE.md
Instructions for teampolarity/cosmos-mcp, covering cosmos-mcp, layout, tools (authoritative list in src/tools/index.ts), cli subcommands and imessage is the headline source.