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/prometheus/prometheus-mcp/agents-mdgit clone --depth 1 https://github.com/prometheus/prometheus-mcpWhat 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.01879 | $0.01879 |
| Opus 5 | $0.00940 | $0.00940 |
| Sonnet 5 | $0.00376 | $0.00376 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
prometheus-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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide for Prometheus MCP Server
An MCP server that exposes a running Prometheus instance (or compatible backend, e.g. Thanos) to LLM clients as typed tools and resources, plus search over an embedded snapshot of the official Prometheus docs (Bleve-indexed at startup). README.md is the canonical reference for the tool list, install methods, auth, telemetry, and flags — when a change affects any of those, update the README rather than duplicating it here.
Build, test, lint
Standard Prometheus tooling: Makefile includes Makefile.common and drives promu; CI is prometheus/promci (.github/workflows/ci.yml). Release artifacts are built in CI, not locally.
| Task | Command |
|---|---|
| Tests | make test |
| Single test while iterating | go test -race -run TestName ./pkg/mcp/ |
| Lint | make lint |
| Full pre-commit check (style, license headers, lint, yamllint, tidy, build, test) | make |
| Build host binary | make build |
| Refresh embedded docs snapshot | make docs |
| List project-specific targets | make help |
Things CI enforces that are easy to miss locally:
- The docs embed.
cmd/prometheus-mcp/main.godeclares//go:embed all:external/docs, and that directory is gitignored —make docspopulates it from a pinnedprometheus/docstarball (DOCS_VERSIONin theMakefile). On a fresh clone, rawgo build ./.../go test ./...fails with a "no matching files" embed error; run any make build/test target once and rawgocommands work from then on (package-scoped commands likego test ./pkg/mcp/don't need the snapshot at all). - License headers. Every source file needs the Apache-2.0 header (
check_licenseruns as part of baremake). Copy it from any existing.gofile when creating a new one. - No drift. CI runs
makeand thengit diff --exit-code— un-tidiedgo.mod/go.sumor anything else the build regenerates must be committed. - golangci-lint (version taken from
make print-golangci-lint-version) andgovulncheckalso gate PRs. - The Go version is pinned in three places —
go.mod,.promu.yml, and the builder image inci.yml. Bump them together.
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.
- 2d ago First seen · 55 lines · 1,879 tokens per session scan A bd7a452a2cc3
prometheus-mcp AGENTS.md is an instructions file published in the GitHub repository prometheus/prometheus-mcp (93 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,879 tokens to every session, about $0.0094 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-30.
Other instructions, from other repositories
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 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.