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/ttcc666/databasemcpserver/agents-mdgit clone --depth 1 https://github.com/ttcc666/DatabaseMcpServerWhat 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.00710 | $0.00710 |
| Opus 5 | $0.00355 | $0.00355 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
DatabaseMcpServer 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Keep solution-level files at the repository root, including
DatabaseMcpServer.slnx,global.json,nuget.config, and MCP config examples. - Main server code lives in
src/DatabaseMcpServer/. Entry points and composition are inProgram.csandExtensions/. - Group runtime logic by responsibility:
Services/for implementations,Interfaces/for contracts,Helpers/for shared parsing/sanitization/configuration utilities,Filters/for cross-cutting MCP filters, andModels/for DTOs. - Tool classes belong under
Tools/Command,Tools/Query,Tools/Documentation,Tools/Export, orTools/Management; keep each tool focused and single-purpose. - CLI and local web configuration code live in
Cli/andWeb/. Tests are intests/DatabaseMcpServer.Tests/. Documentation and database presets are inDoc/andDatabaseSetting/. The optional Vue UI is inwebsite/.
Build, Test, and Development Commands
dotnet build 'DatabaseMcpServer.slnx'— compile the full solution and validate package references.dotnet test 'DatabaseMcpServer.slnx'— run all xUnit tests discovered undertests/.DB_CONNECTION_STRING=... DB_TYPE=MySql dotnet run --project 'src/DatabaseMcpServer/DatabaseMcpServer.csproj'— launch the stdio MCP server for a local smoke test.dotnet pack 'src/DatabaseMcpServer/DatabaseMcpServer.csproj' -c Release— create the NuGet/global-tool package.powershell -ExecutionPolicy Bypass -File scripts/verify.ps1— run repository verification scripts when preparing releases.
Coding Style & Naming Conventions
- Use C# 12 with nullable enabled, implicit usings, four-space indentation, file-scoped namespaces, and braces on the next line.
- Prefer constructor injection and small, testable classes. Reuse shared helpers for SQL safety, connection masking, JSON defaults, and argument validation.
- Use PascalCase for public types and members,
_camelCasefor private readonly fields, and camelCase for parameters/local variables. - Keep comments minimal and rationale-focused. Save text files as UTF-8 without BOM.
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 · 35 lines · 710 tokens per session scan A bf4f87ef4fac
DatabaseMcpServer AGENTS.md is an instructions file published in the GitHub repository ttcc666/DatabaseMcpServer (37 stars, last pushed 27d ago), licensed MIT. It adds 710 tokens to every session, about $0.0036 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
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.
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.