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/mcprunner/mssqlmcp/tsqlgit clone --depth 1 https://github.com/MCPRUNNER/mssqlMCPWrote 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/mcprunner/mssqlmcp/tsql)<a href="https://agentmods.dev/instructions/mcprunner/mssqlmcp/tsql"><img src="https://agentmods.dev/badge/instructions/mcprunner/mssqlmcp/tsql.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.00247 | $0.00247 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
mssqlMCP tsql.instructions.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 3d 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.
What it actually says
T-SQL Instructions
General Guidelines
- Use clear and concise language.
- Follow the T-SQL coding conventions.
- Ensure all code is well-documented using standard SQL comments (
--for single-line and/* ... */for multi-line). - Implement error handling with try catch
- Add logging where appropriate.
- Use meaningful names for variables, tables, and other database objects.
- Optimize queries for performance and efficiency.
- Use transactions where necessary to maintain data integrity.
- Include comments to explain complex logic or business rules.
- Follow best practices for security, such as avoiding SQL injection.
- Use CTEs (Common Table Expressions) for better readability in complex queries.
- Ensure proper indexing strategies are considered in query design.
- Use schema prefixes for all database objects to avoid ambiguity.
- Format SQL code for better readability (indentation, line breaks, etc.).
- Use appropriate data types for columns to optimize storage and performance.
- Regularly review and refactor SQL code to improve performance and maintainability.
- Use column names in INSERT statements for clarity and to avoid errors.
- Avoid using SELECT * in queries; specify the required columns instead.
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.
- 3d ago First seen · 27 lines · 247 tokens per session scan A 225c07fd2d0f
mssqlMCP tsql.instructions.md is an instructions file published in the GitHub repository MCPRUNNER/mssqlMCP (10 stars, last pushed 3mo ago), licensed MIT. It adds 247 tokens to every session, about $0.0012 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
trace-mcp CLAUDE.md
Instructions for nikolai-vysotskyi/trace-mcp, covering trace-mcp development guide, what this project is, agent behavior — read before every task, no flattery, no filler and disagree when the premise is wrong.
MCP-PostgreSQL-Ops copilot-instructions.md
Instructions for call518/MCP-PostgreSQL-Ops, covering architecture overview, core components, key patterns, in functions.py and development workflows.
NyxID CLAUDE.md
Instructions for ChronoAIProject/NyxID, covering project overview, critical rules, 1. mongodb model conventions, 2. layer architecture and 3. error handling.
mcp AGENTS.md
Instructions for Teamwork/mcp, covering agents.md, this repository is public, project overview, setup commands and build and run.
raindrop-mcp GEMINI.md
Instructions for adeze/raindrop-mcp, covering raindrop mcp server - project context, project overview, core technologies, architecture and key commands.
raindrop-mcp copilot-instructions.md
Instructions for adeze/raindrop-mcp: The canonical project instructions are in AGENTS.md. Follow them for architecture, MCP safety constraints, tooling, validation, and release policy.