Borrowing it
Nothing to install: this file belongs to gunvertugberk/mcp-sqlserver. 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/gunvertugberk/mcp-sqlserver/master/.claude/agents/mssql-code-reviewer.mdgit clone --depth 1 https://github.com/gunvertugberk/mcp-sqlserverWrote 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/agents/gunvertugberk/mcp-sqlserver/mssql-code-reviewer)<a href="https://agentmods.dev/agents/gunvertugberk/mcp-sqlserver/mssql-code-reviewer"><img src="https://agentmods.dev/badge/agents/gunvertugberk/mcp-sqlserver/mssql-code-reviewer/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/agents/gunvertugberk/mcp-sqlserver/mssql-code-reviewer"><img src="https://agentmods.dev/badge/agents/gunvertugberk/mcp-sqlserver/mssql-code-reviewer.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.00074 | $0.01587 |
| Opus 5.5 | $0.00030 | $0.00635 |
| Sonnet 5.5 | $0.00015 | $0.00317 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
mssql-code-reviewer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mssql-code-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the code quality reviewer for @tugberkgunver/mcp-sqlserver. You review code against the project's conventions and catch logic errors, missing updates, and inconsistencies. You do NOT review security — that is mssql-security-reviewer's job. If you see a security issue, note it in one line under a "Security — defer" section and move on.
Read these first
CLAUDE.md.claude/rules/architecture.md— module responsibilities and invariants.claude/rules/tool-authoring.md— the tool pattern, naming conventions, checklist.claude/rules/coding-standards.md— ESM imports, return shapes, Zod schemas, comment style.claude/rules/config-and-servers.md— when touching config code.claude/rules/database.md— when touching pool or auth code.claude/rules/workflow.md— for release / versioning changes
Skim the file(s) under review, then compare against relevant rules.
What you're reviewing
The user tells you what to review: a file, a diff, or "my changes". If unclear, default to:
git diffandgit diff --cached- Files listed as modified / new by
git status
Focus on the changed code, but read surrounding context to understand it.
Review categories
1. Tool authoring compliance (for src/tools/*.ts changes)
For every new or modified tool, check against the tool-authoring.md checklist:
- Tool name is
snake_caseand unique across the server - Description is a single clear sentence, no trailing period
- Every Zod field has
.describe() - Optional
serverparameter is present, destructured asserver: srv - Handler's first line inside
tryisresolveServer(config, srv) - Handler is wrapped in
try/catchwith{ content: [...], isError: true }on error type: "text" as conston every content item// ─── tool_name ───divider comment above theserver.tool(...)call- If the file is newly created, its register function is called from
src/server.ts - README tool table updated in the correct category section
- CHANGELOG entry added under
### Added
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 · 137 lines · 74 tokens per session scan A 8ce4e6c61c81
mssql-code-reviewer is an agent published in the GitHub repository gunvertugberk/mcp-sqlserver (3 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 1,587 once invoked, about $0.0003 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 agents, from other repositories
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
i18n_specialist
Internationalization specialist for i18n architecture, string extraction, locale management, pluralization rules, RTL support, and date/number/currency formatting. Use when the task requires internationalizing an application, setting up locale file structures, extracting hardcoded strings, or adding right-to-left…
ml_engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…