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-intelligencenpx skills add CartapenaBark/DotNetAnalyzer --skill dotnet-analyzer-code-intelligencegit clone --depth 1 https://github.com/CartapenaBark/DotNetAnalyzerWhat 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.00226 | $0.01150 |
| Opus 5 | $0.00113 | $0.00575 |
| Sonnet 5 | $0.00045 | $0.00230 |
| Haiku 4.5 | $0.00023 | $0.00115 |
Grade A, and why
dotnet-analyzer-code-intelligence 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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Code Intelligence
Navigate and understand C# code through symbol queries, type hierarchies, call graphs, and semantic analysis.
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 |
|---|---|---|
find_references |
Find all references to a symbol | projectPath, filePath, line, column |
find_declarations |
Find symbol declaration locations | projectPath, filePath, line, column |
get_symbol_info |
Get detailed symbol metadata | projectPath, filePath, line, column |
resolve_symbol |
Resolve a symbol by name | projectPath, filePath, line, column |
go_to_definition |
Jump to symbol definition | filePath, line, column |
get_type_hierarchy |
Full type inheritance chain | projectPath, typeName |
get_member_hierarchy |
Member override/implementation chain | projectPath, memberName, containingType |
get_semantic_model |
Semantic info at a position | filePath, line, column |
get_syntax_tree |
Syntax tree structure as JSON | filePath, optional range, maxDepth |
get_code_metrics |
Complexity and quality metrics | projectPath, filePath |
get_caller_info |
Find all callers of a method | projectPath, filePath, line, column |
get_callee_info |
Find all methods called by a method | projectPath, filePath, line, column |
get_call_graph |
Generate call graph (DOT/JSON/Mermaid) | projectPath, filePath, optional format |
get_definition_and_references |
Combined definition + references | projectPath, filePath, line, column |
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.
- 2d ago First seen · 92 lines · 226 tokens per session scan A 09a981ed110a
dotnet-analyzer-code-intelligence is a skill published in the GitHub repository CartapenaBark/DotNetAnalyzer (2 stars, last pushed 4mo ago), licensed MIT. It adds 226 tokens to every session and 1,150 once invoked, about $0.0011 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
roslyn-codelens
Use when working with any .NET / C# code (.cs/.csproj/.sln/.slnx files), finding callers/references/implementations, checking compiler errors or warnings, running dotnet build for diagnostics, searching for a type/method/interface by name, inspecting DI registrations, detecting dead code or circular dependencies…
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
csharp-azure-spector-coverage-gaps
Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…
mgmt-review-comment-resolution
Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.
mpg-migration
Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec; use for MPG, mgmt migration, or Azure.ResourceManager. migration requests.
bump-mgmt-base-version
Bump the http-client-csharp base dependency version in http-client-csharp-mgmt. Updates emitter (npm) and generator (NuGet) references, rebuilds, and regenerates test projects.