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-actionsgit 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-actions)<a href="https://agentmods.dev/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-actions"><img src="https://agentmods.dev/badge/skills/cartapenabark/dotnetanalyzer/dotnet-analyzer-actions.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.1 | $0.00319 | $0.01575 |
| Opus 5 | $0.00160 | $0.00788 |
| Sonnet 5 | $0.00064 | $0.00315 |
| Haiku 4.5 | $0.00032 | $0.00158 |
Grade A, and why
dotnet-analyzer-actions 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Code Actions
Perform refactoring, code generation, project operations, decompilation, XAML analysis, and desktop pattern detection.
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__):
Refactoring
| Tool | Purpose |
|---|---|
extract_method |
Extract selected code into a new method |
rename_symbol |
Rename a symbol across all references |
introduce_variable |
Introduce a local variable for an expression |
encapsulate_field |
Convert field to property with backing field |
extract_interface |
Extract public members into an interface |
change_signature |
Add/remove/reorder method parameters |
add_parameter |
Add a parameter to a method |
inline_temporary |
Inline a temporary variable |
safely_remove_as |
Remove unnecessary as cast |
remove_unnecessary_code |
Remove dead/redundant code |
convert_for_to_foreach |
Convert for loop to foreach |
convert_foreach_to_for |
Convert foreach to for loop |
convert_if_to_switch |
Convert if chain to switch |
reverse_for_statement |
Reverse for loop direction |
list_refactorers |
List available refactorers |
Code Generation
| Tool | Purpose |
|---|---|
generate_interface_impl |
Generate interface implementation stubs |
generate_constructor |
Generate constructor from fields/properties |
generate_property |
Generate auto/full property |
generate_deconstructor |
Generate deconstructor (tuple pattern) |
generate_from_usage |
Generate type/member from usage |
remove_unused_usings |
Remove unused using directives |
sort_usings |
Sort using directives (System → Third-party → Local) |
add_missing_imports |
Add missing namespace imports |
organize_imports |
Remove unused + sort in one pass |
format_selection |
Format selected code |
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.
- 7d ago First seen · 160 lines · 319 tokens per session scan A eedbab9e9e1a
dotnet-analyzer-actions is a skill published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 4mo ago), licensed MIT. It adds 319 tokens to every session and 1,575 once invoked, about $0.0016 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
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
truecourse-fix
Fix TrueCourse violations that have suggested fixes.
truecourse-list
List TrueCourse violations found in this repository.
optimization-audit
Comprehensive optimization audit with two modes and a single tier. Planning mode designs performance strategy, capacity planning, and scaling architecture. Audit mode scans code and infrastructure for performance anti-patterns, inefficient algorithms, N+1 queries, missing caching, concurrency issues, and resource…
cognitive-interface-audit
Comprehensive cognitive interface audit with two modes and a single tier. Planning mode designs task models, user expertise mapping, and error tolerance strategy. Audit mode evaluates mental model alignment (Norman's Gulfs), consistency (Gestalt), error tolerance (Wood 7-layer defense), cognitive load (NASA-TLX…
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.