agentmods.dev

report

report is a command for Claude Code from CartapenaBark/DotNetAnalyzer. It costs 25 tokens per session (841 once invoked), scanned A, original, MIT.

A command for generating a quality report for a .NET project or solution. It examines code problems, technical debt, architecture rules, and dependencies.

In plain words
What is it for?
Use it to analyse a specified or automatically detected .NET solution, including compiler diagnostics, code smells, architecture compliance, and dependency health.
Why use it?
It gives developers a structured view of risks and maintenance problems that may be missed during ordinary compilation.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the netan plugin — 5 skills, 3 commands shipped together

not rated 2repo 6mo ago A scan 25 tokens original MIT

Good fit Use it to analyse a specified or automatically detected .NET solution, including compiler diagnostics, code smells, architecture compliance, and dependency health.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/cartapenabark/dotnetanalyzer/report
View source ↗ CartapenaBark/DotNetAnalyzer
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.

Clone the repo
git clone --depth 1 https://github.com/CartapenaBark/DotNetAnalyzer

Made for: Claude Code.

Or install netan, the plugin that ships this one along with the rest of its 5 skills, 3 commands.

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

agentmods badge for report

README.md
[![agentmods](https://agentmods.dev/badge/commands/cartapenabark/dotnetanalyzer/report/github.svg)](https://agentmods.dev/commands/cartapenabark/dotnetanalyzer/report)
Your own site
<a href="https://agentmods.dev/commands/cartapenabark/dotnetanalyzer/report"><img src="https://agentmods.dev/badge/commands/cartapenabark/dotnetanalyzer/report/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.

agentmods 80×15 button for report

Your own site · 80×15
<a href="https://agentmods.dev/commands/cartapenabark/dotnetanalyzer/report"><img src="https://agentmods.dev/badge/commands/cartapenabark/dotnetanalyzer/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 841 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00841
Opus 5.5 $0.00010 $0.00336
Sonnet 5.5 $0.00005 $0.00168
Haiku 4.5 $0.00003 $0.00084

Measured 1mo ago against content hash 673ab035d918, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugin/commands/report.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/netan:report — .NET Quality Report

Generate a comprehensive quality report covering code smells, technical debt metrics, architecture rule compliance, and dependency health.

Prerequisite Check

  1. Run dotnet-analyzer --version to verify the global tool is installed
  2. If it fails, ask the user: "DotNetAnalyzer global tool is not installed. Shall I run dotnet tool install --global DotNetAnalyzer for you?"
    • If confirmed, run dotnet tool install --global DotNetAnalyzer and continue
    • If declined, provide the manual install command and stop

Arguments

The user may optionally provide a project or solution path:

  • If provided: use that path directly
  • If not provided: auto-detect by looking for *.slnx or *.sln in the current working directory
  • If no solution file found: ask the user for the path

Steps

  1. Identify the target:

    • Use the provided path, or auto-detect *.slnx / *.sln in the current directory

  2. Get compiler diagnostics:

    • Call get_diagnostics to establish baseline compilation status
    • If compilation errors exist, report them first and flag that other analysis may be incomplete

  3. Detect code smells:

    • Call detect_code_smells with minSeverity: "Minor"
    • Collect all smell types and severity levels

  4. Quantify technical debt:

    • Call quantify_technical_debt for debt ratio and fix estimates
    • Note debt level (Excellent/Good/Moderate/High/Severe)

  5. Check architecture rules:

    • Call check_architecture_rules for dependency direction, layer hierarchy, and naming violations

  6. Scan dependency health:

    • Call scan_dependencies_health for overall health score

  7. Generate comprehensive report:

    ## Quality Report: [Project/Solution Name]

### Executive Summary
- Compilation: [Pass/Fail] (N errors, N warnings)
- Code Smells: N found (N major, N minor)
- Technical Debt: [N hours] — [Severity level]
- Architecture: [N violations]
- Dependency Health: [N/100]

### Compiler Diagnostics
- Errors: N (must fix)
- Warnings: N
- [List top issues if any]

### Code Smells
| Type | Severity | Location | Description |
|------|----------|----------|-------------|
| Long Method | Major | ... | 85 lines, CC=18 |

### Technical Debt
- Debt Ratio: N hours / 1000 LOC
- Estimated Fix Time: N hours
- Top 5 Items:
  1. [Item] — [N hours]
  2. ...

### Architecture Rules
| Rule | Violations | Severity |
|------|-----------|----------|
| AR001 Dependency Direction | N | Error/Warning |
| AR002 Layer Hierarchy | N | Error/Warning |
| AR003 Naming Convention | N | Error/Warning |

### Dependency Health
- Score: N/100
- Outdated: N | Deprecated: N | Vulnerable: N
- [Key action items]

### Priority Action Items
1. [Most impactful fix]
2. [Second most impactful]
3. ...

Read the full file on GitHub · 99 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.

  1. 1mo ago First seen · 99 lines · 25 tokens per session scan A 673ab035d918

Subscribe to this mod's changes

report is a command published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 841 once invoked, about $0.0001 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.

Claude CodePlanningarchitectureclaude-code-plugincode-analysisdotnet
Related

Other commands, from other repositories

feedback

A design-stage security review for product requirement documents and other planning documents; a PRD is a document describing what a product should do.

ch015/code-pentester · 21 tokens

compliance

A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.

ch015/code-pentester · 32 tokens

pentest

A read-only penetration-testing command for examining source code from an attacker’s perspective and producing proof-of-concept checks. Penetration testing is authorized security testing that tries to verify exploitable weaknesses.

ch015/code-pentester · 27 tokens

va

A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.

ch015/code-pentester · 21 tokens

verify

An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.

ch015/code-pentester · 20 tokens

redteam

A read-only review of infrastructure settings, infrastructure-as-code, and CI/CD pipelines using MITRE ATT&CK attack paths. MITRE ATT&CK is a catalogue of techniques attackers use, while CI/CD means the automated process that builds, tests, and deploys software.

ch015/code-pentester · 20 tokens