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 skills add CartapenaBark/DotNetAnalyzer --skill dotnet-analyzer-code-qualitygit clone --depth 1 https://github.com/CartapenaBark/DotNetAnalyzerWrote 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/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-quality)<a href="https://agentmods.dev/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-quality"><img src="https://agentmods.dev/badge/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-quality/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/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-quality"><img src="https://agentmods.dev/badge/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-quality.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.00242 | $0.01041 |
| Opus 5.5 | $0.00097 | $0.00416 |
| Sonnet 5.5 | $0.00048 | $0.00208 |
| Haiku 4.5 | $0.00024 | $0.00104 |
Grade A, and why
dotnet-analyzer-code-quality 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Code Quality Analysis
Detect and quantify code quality issues, architecture violations, and technical debt in .NET projects.
Prerequisite Check
Before any analysis, verify dotnet-analyzer is installed:
- Run
dotnet-analyzer --versionin a shell - If it fails, ask the user: "DotNetAnalyzer global tool is not installed. Shall I run
dotnet tool install --global DotNetAnalyzerfor you?"- If confirmed, run the install command and continue
- If declined, provide the manual install command and stop
Available MCP Tools
Use these MCP tools (prefixed with mcp__plugin_netan_dotnet-analyzer__):
| Tool | Purpose | Key Parameters |
|---|---|---|
detect_code_smells |
Detect 12 types of code smells | projectPath, optional minSeverity |
quantify_technical_debt |
Quantify tech debt in hours | projectPath, optional includeTrend |
generate_quality_report |
Comprehensive quality report | projectPath |
get_diagnostics |
Compiler errors, warnings, info | projectPath, optional filePath |
find_dead_code |
Find unused types and methods | projectPath |
analyze_performance |
Identify performance bottlenecks | projectPath |
generate_heatmap |
Complexity or change-frequency heatmap | projectPath, type |
generate_dependency_graph |
Dependency graph (Mermaid/JSON/DOT) | projectPath, optional format |
check_architecture_rules |
Check architecture constraints (SARIF) | projectPath |
Workflow
Quick Quality Check
- Get diagnostics: Call
get_diagnosticsfor compiler errors/warnings - Detect code smells: Call
detect_code_smellswithminSeverity: "Major" - Summarize: Present error count, warning count, and top code smells
Comprehensive Quality Report
- Diagnostics:
get_diagnosticsfor compilation status - Code smells:
detect_code_smellsfor all severity levels - Technical debt:
quantify_technical_debtfor debt estimates - Architecture:
check_architecture_rulesfor dependency violations - Dead code:
find_dead_codefor unused code - Performance:
analyze_performancefor bottlenecks - Report: Call
generate_quality_reportfor combined output
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 · 93 lines · 242 tokens per session scan A f3ff32b1b3e6
dotnet-analyzer-code-quality is a skill published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 6mo ago), licensed MIT. It adds 242 tokens to every session and 1,041 once invoked, about $0.0010 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 skills, from other repositories
river-review-architecture
An architecture-review guide that checks whether software design decisions, system boundaries, and data models fit together consistently. An architecture review examines the structure and dependencies of a system.
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…
ch015-verifier
Run CH015 adversarial verification workflows to independently validate security reports, recheck file-line evidence, find false positives, severity errors, missed findings, and dependencies.
ch015-pentest
Run CH015 penetration testing workflows for attacker-minded source-code review, exploit scenarios, POC generation, dry-run or live verification, and security findings.
review
The definitive code review, for any codebase. Five-phase workflow: git context detection (worktree, branch, base, changed files), Pharaoh recon (architecture map, module context, blast radius in one call, with a fallback when the repo isn't mapped), parallel specialized agent dispatch (code quality, security against…
ADR Decision Quality
Ensure ADRs capture context, decision, alternatives, tradeoffs, and follow-ups in a way that prevents future drift.