Borrowing it
Nothing to install: this file belongs to therealtimex/un-datacommons-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/therealtimex/un-datacommons-mcp/realtimex/AGENTS.mdgit clone --depth 1 https://github.com/therealtimex/un-datacommons-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/therealtimex/un-datacommons-mcp/agents-md)<a href="https://agentmods.dev/instructions/therealtimex/un-datacommons-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/therealtimex/un-datacommons-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.1 | $0.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
un-datacommons-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 6d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
This repository hosts the Data Commons MCP server and tooling as a Python (uv) workspace. The primary package lives under packages/un-datacommons-mcp.
Project Structure & Module Organization
packages/un-datacommons-mcp/datacommons_mcp/: core code —server.py(FastAPI server),cli.py(entrypoint),services.py,clients.py,topics.py,data_models/*,data/*.packages/un-datacommons-mcp/tests/: pytest tests.docs/: user and internal docs; images indocs/*.png..github/workflows/: CI, build, and publish workflows.- Root
pyproject.toml: uv workspace + shared tools; package-specificpyproject.tomlinpackages/un-datacommons-mcp.
Build, Test, and Development Commands
- Install deps:
uv sync - Format:
uv run ruff format(check only:uv run ruff format --check) - Lint:
uv run ruff check - Tests (skip evals):
uv run --extra test pytest -k "not eval" - Run server (HTTP):
uvx un-datacommons-mcp serve http --port 8080 - Run server (stdio):
uvx un-datacommons-mcp serve stdio
Coding Style & Naming Conventions
- Python 3.11–3.12, 4‑space indentation, one import per line (isort via Ruff).
- Prefer type hints for public APIs; follow
N*andANN*rules inpyproject.toml. - Use double quotes; keep functions small and explicit (avoid broad
exceptwhere practical). - Module naming:
snake_case.py; classesPascalCase; functions/varssnake_case.
Testing Guidelines
- Frameworks:
pytest,pytest-asyncio. - Location:
packages/un-datacommons-mcp/tests/; name teststest_*.py. - Run unit tests locally:
uv run --extra test pytest -k "not eval". - Add tests for new features/bugfixes; prefer fast, deterministic tests. Mark or separate any network-dependent tests.
Commit & Pull Request Guidelines
- Commits: imperative, present tense (e.g., "Add settings validation"); group related changes. Reference issues (e.g.,
#123). - Before pushing: run formatter, linter, and tests.
- Optional hook:
uv run pre-commit install --hook-type pre-pushthen rely on configuredruffandpytestchecks. - PRs: clear description, rationale, linked issues, and test updates. CI must pass.
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.
- 6d ago First seen · 42 lines · 687 tokens per session scan A 4579bf24715b
un-datacommons-mcp AGENTS.md is an instructions file published in the GitHub repository therealtimex/un-datacommons-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 687 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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).
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.
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.