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/kalcifield/eea-climate-data-mcp/agents-mdgit clone --depth 1 https://github.com/kalcifield/eea-climate-data-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/kalcifield/eea-climate-data-mcp/agents-md)<a href="https://agentmods.dev/instructions/kalcifield/eea-climate-data-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kalcifield/eea-climate-data-mcp/agents-md.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.00783 | $0.00783 |
| Opus 5 | $0.00392 | $0.00392 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
eea-climate-data-mcp 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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure
Python uses the src layout under src/eea_climate_data/. Keep typed data contracts
in models.py, workflows in service.py, SQL safety in sql_validation.py, upstream
wire behavior in discodata.py, and verified EEA table semantics in profile.py. Keep
cli.py and mcp_server.py thin; both must call the same ClimatePolicyService
methods. Design findings and live evidence belong in docs/.
Development Commands
Use Python 3.11+ and uv:
uv sync --extra test
uv run eu-climate --help
uv run eea-climate-data-mcp
uv run pytest -q
uv run ruff format --check src tests
uv run ruff check src tests
uv run mypy src tests
Release with scripts/release {patch|minor|major}. GitHub Actions publishes to PyPI
through the pypi environment after the GitHub Release is created.
Run uv run python scripts/live_smoke.py only when explicitly validating the public
service. Keep live probes small, bounded, read-only, and separate from routine tests.
Code and Interface Conventions
Use type annotations and Pydantic models at public boundaries. Modules, functions, and
variables use snake_case; classes and models use PascalCase. Preserve upstream field
names in provider payloads and normalized semantics in domain models. Machine-readable
output goes to stdout; diagnostics go to stderr. JSON and JSONL output must remain
semantically equivalent. Avoid provider logic in CLI or MCP adapters.
SQL Safety
Never weaken the single-statement, SELECT-only, database/version allowlist,
fully-qualified-table, row-bound, page-size, timeout, computed-alias, or system-schema
guardrails. Continue using a T-SQL parser; regex alone must not authorize queries. Block
DDL, DML, execution, transactions, SELECT INTO, CTEs, and unsupported system objects.
Warn when pagination lacks deterministic ordering. Do not log raw SQL containing user
literals. Query results are deliberately not cached unless a reviewed design changes
that policy.
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 · 75 lines · 783 tokens per session scan A a23828b26653
eea-climate-data-mcp AGENTS.md is an instructions file published in the GitHub repository kalcifield/eea-climate-data-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 783 tokens to every session, about $0.0039 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
meteoswiss-mcp CLAUDE.md
Claude Code instructions for malkreide/meteoswiss-mcp, covering claude.md, vor der arbeit, tests, wenn etwas rot ist and wenn codex gar nicht erst hinsieht.
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.
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 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.