What is SqlAugur AGENTS.md?

A project guide for SqlAugur, a .NET MCP server that lets AI assistants use defined tools. It describes the code layout, commands, style rules, and tests.

Use it when changing SqlAugur code, running unit or container-based integration tests, or creating its release and NuGet package.

It gives a coding agent the repository’s working rules and the correct commands for building, testing, running, and packaging the server.

SqlAugur AGENTS.md — Instructions file by mbentham

Install

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.

agentmods

npx agentmods add instructions/mbentham/sqlaugur/agents-md

Clone the repo

git clone --depth 1 https://github.com/mbentham/SqlAugur

Made for: Codex, OpenCode.

Per session 650 This file is loaded in full into every session.

When invoked 650 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00650	$0.00650
Opus 5	$0.00325	$0.00325
Sonnet 5	$0.00130	$0.00130
Haiku 4.5	$0.00065	$0.00065

Measured yesterday against content hash 05393d6ce7cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

AGENTS.md · 43 lines

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.0 with nullable and implicit usings enabled.
Indentation: 4 spaces; keep formatting consistent with existing files.
Naming: PascalCase for types/methods/properties; camelCase for locals/parameters; interfaces prefixed with I (for example ISqlServerService).
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.Sdk and coverlet.collector.
Test file naming: *Tests.cs (for example QueryValidatorTests.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"

Read the full file on GitHub · 43 lines

Changes

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.

yesterday First seen · 43 lines · 650 tokens per session scan A 05393d6ce7cb

Subscribe to this mod's changes

SqlAugur AGENTS.md is an instructions file published in the GitHub repository mbentham/SqlAugur (5 stars, last pushed 1mo ago), licensed MIT. It adds 650 tokens to every session, about $0.0032 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.

Data and AI Git and workflow LLM Testing ai csharp dba dotnet mcp-server

nina AGENTS.md

Instructions for isbeorn/nina, covering agents.md, scope, documentation boundary, repository knowledge and code style and formatting.

isbeorn/nina · 2,701 tokens

bitfinex-net

Use Bitfinex.Net when generating C#/.NET code that interacts with Bitfinex, including Spot, margin, derivatives symbols, funding, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on Bitfinex integration requests in C#, .NET, dotnet, F#, or VB.NET context.

JKorf/Bitfinex.Net · 1,639 tokens

SqlAugur AGENTS.md