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/meob/mcp-blueprint/agents-mdgit clone --depth 1 https://github.com/meob/mcp-blueprintWrote 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/meob/mcp-blueprint/agents-md)<a href="https://agentmods.dev/instructions/meob/mcp-blueprint/agents-md"><img src="https://agentmods.dev/badge/instructions/meob/mcp-blueprint/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.00688 | $0.00688 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
mcp-blueprint 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Servers
This project exposes several MCP Blueprint servers. Each server name is
prefixed to its tool names (e.g. pg-dba-docker_get_connections), so the
server a tool runs against is always identifiable from the tool name.
| Server | Transport | Engine | Pack | Target database |
|---|---|---|---|---|
pg-dba |
stdio | PostgreSQL | pg-dba | Local pgbench database on localhost:5432 |
pg-sakila |
stdio | PostgreSQL | sakila | Local sakila database on localhost:5432 |
mysql-dba |
stdio | MySQL | mysql-dba | Local mysakila database on localhost:3306 |
mysql-dba-docker |
stdio | MySQL | mysql-dba | Containerized MySQL 8 mysakila on localhost:3308 |
pg-dba-docker |
remote | PostgreSQL | pg-dba | Containerized PostgreSQL 16 (docker compose stack) |
oracle-dba |
stdio | Oracle | oracle-dba | Containerized Oracle 23 (PDB FREEPDB1) on localhost:1521 |
clickhouse-dba |
stdio | ClickHouse | clickhouse-dba | Containerized ClickHouse 24.8 on localhost:9000 |
sqlserver-dba |
stdio | SQL Server | sqlserver-dba | Containerized SQL Server 2022 on localhost:1433 |
mariadb-dba |
stdio | MariaDB | mariadb-dba | Containerized MariaDB 11.4 mysakila on localhost:3307 |
smoke |
stdio | SQLite | smoke | In-memory SQLite database (no external server) |
Routing rules
- Always call the tool whose server prefix matches the target environment.
- "the Docker / containerized database" -> use
pg-dba-docker_*tools. - "the local PostgreSQL / localhost" -> use
pg-dba_*tools. - "the local MySQL / localhost" -> use
mysql-dba_*tools. - "the containerized MySQL / 3308" -> use
mysql-dba-docker_*tools. - Sakila store questions -> use
pg-sakila_*tools. - MySQL questions -> use
mysql-dba_*tools. - Oracle container questions -> use
oracle-dba_*tools. - ClickHouse container questions -> use
clickhouse-dba_*tools. - SQL Server container questions -> use
sqlserver-dba_*tools. - MariaDB container questions -> use
mariadb-dba_*tools. - "the smoke / deployment test server" -> use
smoke_*tools (smoke_ping,smoke_get_server_status,smoke_fortune,smoke_horoscope). - When the target is ambiguous, ask which server to use instead of guessing.
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 · 36 lines · 688 tokens per session scan A a5cf1d51421f
mcp-blueprint AGENTS.md is an instructions file published in the GitHub repository meob/mcp-blueprint (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 688 tokens to every session, about $0.0034 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.
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).