Borrowing it
Nothing to install: this file belongs to mbentham/SqlAugur. 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/mbentham/SqlAugur/main/AGENTS.mdgit clone --depth 1 https://github.com/mbentham/SqlAugurWrote 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/mbentham/sqlaugur/agents-md)<a href="https://agentmods.dev/instructions/mbentham/sqlaugur/agents-md"><img src="https://agentmods.dev/badge/instructions/mbentham/sqlaugur/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/mbentham/sqlaugur/agents-md"><img src="https://agentmods.dev/badge/instructions/mbentham/sqlaugur/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.00650 | $0.00650 |
| Opus 5.5 | $0.00260 | $0.00260 |
| Sonnet 5.5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
SqlAugur 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 2mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
SqlAugur/: main MCP server (Program.cs) and production code.SqlAugur/Tools/: MCP tool endpoints (thin wrappers with[McpServerTool]).SqlAugur/Services/: business logic and SQL access (validation, schema, DBA integrations).SqlAugur/Configuration/: options, validators, and toolset registry.SqlAugur.Tests/: unit tests (xUnit v3, no external services).SqlAugur.IntegrationTests/: container-backed integration tests (SQL Server via Testcontainers/Podman).- Root docs:
README.md,CONTRIBUTING.md,SECURITY.md,CHANGELOG.md.
Build, Test, and Development Commands
dotnet build: build the full solution from repo root (SqlAugur.slnx).dotnet run --project SqlAugur: run the MCP server on stdio.dotnet test SqlAugur.Tests: run unit tests only.DOCKER_HOST=unix:///run/user/1000/podman/podman.sock TESTCONTAINERS_RYUK_DISABLED=true dotnet test SqlAugur.IntegrationTests: run integration tests.dotnet publish SqlAugur -c Release -o SqlAugur/publish: produce release output.dotnet pack SqlAugur -c Release: build the NuGet global tool package.
Coding Style & Naming Conventions
- Language: C# on
net10.0with nullable and implicit usings enabled. - Indentation: 4 spaces; keep formatting consistent with existing files.
- Naming:
PascalCasefor types/methods/properties;camelCasefor locals/parameters; interfaces prefixed withI(for exampleISqlServerService). - Design rule: keep tools thin; put behavior in services.
- Security-sensitive logic (especially query validation) should remain AST-based, not regex-based.
Testing Guidelines
- Framework: xUnit v3 with
Microsoft.NET.Test.Sdkandcoverlet.collector. - Test file naming:
*Tests.cs(for exampleQueryValidatorTests.cs). - Add or update tests for all behavior changes; include bypass/regression cases for validator changes.
- Helpful filters:
dotnet test --filter "DisplayName~TestNameHere"dotnet test --filter "FullyQualifiedName~QueryValidatorTests"
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.
- 2mo ago First seen · 43 lines · 650 tokens per session scan A 05393d6ce7cb
SqlAugur AGENTS.md is an instructions file published in the GitHub repository mbentham/SqlAugur (8 stars, last pushed 17d ago), licensed MIT. It adds 650 tokens to every session, about $0.0026 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.