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 skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-code-qualitynpx 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.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.00242 | $0.01041 |
| Opus 5 | $0.00121 | $0.00521 |
| Sonnet 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 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.
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.
- 3d 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 4mo ago), licensed MIT. It adds 242 tokens to every session and 1,041 once invoked, 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 skills, from other repositories
dotnet-read
Use when reading or navigating C#/.NET code — find or search for a class, interface, method, property or field; read a symbol's source; look up who calls something or what implements it; trace a call tree or a path between two functions; see what is callable at a line; inspect a base chain or project references; find…
dotnet-write
Use when writing, adding, editing, modifying, patching, refactoring, renaming or deleting C#/.NET code — changing a method or type, changing a signature, adding a class or a file, fixing a compile error or an analyzer warning, or applying review findings. Validates every edit against an in-memory compilation before it…
dotnet-review
Use when the user asks to review C#/.NET code, check a PR/diff, look for naming or styling issues, assess performance or concurrency, find dead code/duplication, review XML documentation, check test coverage, or do a security review. ALSO use it for a convention or consistency audit across existing code — "are all our…
dotnet-explore
Use before changing C#/.NET code when the set of symbols the task touches is not already known — surveying an unfamiliar subsystem, assessing how a new feature lands in the existing codebase, or finding out what a change would break. Delegates the wide searchindex/getreferences sweep to the plugin's dotnet-explore…
dotnet-init
Use when the user asks to set up, install, wire up, verify, refresh, or remove dotnet-toolkit in a project — "set up dotnet-toolkit here", "/dotnet-init", "make Claude use the MCP tools in this repo", and equally "did the init work", "check the dotnet-toolkit installation", "is this repo wired up correctly", "are my…
grasshopper-component
Complete guide for developing custom Grasshopper components in C# — GHComponent class, RegisterInputParams/OutputParams, SolveInstance, DataTree patterns, parameter types, error handling, and component packaging as .gha. Use this skill whenever creating or debugging a Grasshopper component: "grasshopper component c#"…