Borrowing it
Nothing to install: this file belongs to phatngoit/MCP-DB. 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/phatngoit/MCP-DB/master/AGENTS.mdgit clone --depth 1 https://github.com/phatngoit/MCP-DBWrote 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/phatngoit/mcp-db/agents-md)<a href="https://agentmods.dev/instructions/phatngoit/mcp-db/agents-md"><img src="https://agentmods.dev/badge/instructions/phatngoit/mcp-db/agents-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/phatngoit/mcp-db/agents-md"><img src="https://agentmods.dev/badge/instructions/phatngoit/mcp-db/agents-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.01312 | $0.01312 |
| Opus 5.5 | $0.00525 | $0.00525 |
| Sonnet 5.5 | $0.00262 | $0.00262 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
MCP-DB 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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This is a TypeScript Node.js MCP server for readonly-first database access. Source files live in src/: cli.ts is the command entry point, server.ts starts the MCP server, config/ validates YAML configuration, connectors/ contains Oracle, MSSQL, and MongoDB adapters, core/ holds shared security/audit logic, and tools/ registers MCP tools. Tests are colocated as *.test.ts, for example src/core/security.test.ts. Documentation is in docs/, sample configs are in examples/, and compiled output goes to dist/.
Build, Test, and Development Commands
npm install: install dependencies; Node.js>=20.10is required.npm run dev -- start --config ./mcp-db.local.yml: run the CLI from TypeScript viatsx.npm run build: compile TypeScript usingtsconfig.build.jsonintodist/.npm run start -- --config ./mcp-db.local.yml: run the compiled CLI entry point.npm run typecheck: run strict TypeScript checks without emitting files.npm run test: run Vitest tests once.npm run format: format TypeScript, Markdown, JSON, YAML, and YML files with Prettier.npm run lint: run ESLint oversrc/**/*.ts; ensure an ESLint config exists before relying on CI.
Coding Style & Naming Conventions
Use ES modules and strict TypeScript. Follow Prettier settings: single quotes, semicolons, trailing commas, and a 100-character print width. Use kebab-case filenames such as load-config.ts and register-tools.ts. Prefer named exports for shared utilities and explicit types at connector and MCP tool boundaries.
Testing Guidelines
Vitest is the test framework. Add focused *.test.ts files next to the code they cover. Use descriptive describe blocks and it cases such as it('blocks SQL writes', ...). Run npm run typecheck and npm run test before submitting changes. Security-sensitive code, config validation, and connectors should test both allowed and blocked paths.
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.
- 1mo ago First seen · 77 lines · 1,312 tokens per session scan A d513edb49680
MCP-DB AGENTS.md is an instructions file published in the GitHub repository phatngoit/MCP-DB (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,312 tokens to every session, about $0.0052 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.