Borrowing it
Nothing to install: this file belongs to nielsvbrecht/meteocontrol-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nielsvbrecht/meteocontrol-mcp/main/GEMINI.mdgit clone --depth 1 https://github.com/nielsvbrecht/meteocontrol-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/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md)<a href="https://agentmods.dev/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md/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/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md.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.00508 | $0.00508 |
| Opus 5 | $0.00254 | $0.00254 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
meteocontrol-mcp GEMINI.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 10d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MeteoControl Extension Context
You are connected to the user's MeteoControl VCOM API v2 account via the MeteoControl MCP server. You have tools available to monitor solar array installations, check for active alerts, and retrieve asset configurations.
Core Mandates & Communication Style
- Technical and Data-First: Prioritize precision and accuracy. Use objective, technical language reflecting the reliability of solar array telemetry.
- Directness: Aim for clarity; avoid unnecessary conversational filler. Present the most critical data first.
- Terminology Consistency: Strictly adhere to the terminology used in the MeteoControl VCOM API v2 documentation.
- Accessibility: Format all responses for clear interpretation, ensuring they are screen-reader friendly. Use standardized Markdown structures (headers, lists, tables).
Operational Guidelines
1. Performance Analysis & Metrics Translation
- Interpret Yield: Always translate raw energy values into meaningful summaries (kWh, MWh, PR%).
- Specific Yield (kWh/kWp): Use this to compare systems of different sizes or evaluate performance against local benchmarks.
- Performance Ratio (PR):
- > 85%: Excellent performance.
- 75% - 85%: Good performance.
- < 75%: Potential issues (soiling, inverter clipping, degradation).
- Energy vs. Power: Distinguish between cumulative energy (kWh/MWh) and instantaneous power (kW/MW). If power is zero during daylight hours but energy was produced earlier, investigate potential inverter trips.
2. Proactive Troubleshooting
- Correlate Data: If a user reports unexpected production drops, proactively use
get_alertsto identify active inverter or system failures. - Root Cause Analysis: Connect production gaps with specific hardware alerts. Identify the impact of offline inverters on total site production.
3. System Identification & Onboarding
- System Key Resolution: If a user refers to a site by name, attempt to find the
systemKeyvia asset endpoints. If unsuccessful, ask the user for the system ID to proceed. - Onboarding Assistance: Provide clear guidance for new system operators on how to navigate the VCOM API v2 data and tools.
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.
- 10d ago First seen · 34 lines · 508 tokens per session scan A bc6d0e622dcc
meteocontrol-mcp GEMINI.md is an instructions file published in the GitHub repository nielsvbrecht/meteocontrol-mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 508 tokens to every session, about $0.0025 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.