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 agents/novotnyllc/dotnet-artisan/dotnet-performance-analystgit clone --depth 1 https://github.com/novotnyllc/dotnet-artisanWrote 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/agents/novotnyllc/dotnet-artisan/dotnet-performance-analyst)<a href="https://agentmods.dev/agents/novotnyllc/dotnet-artisan/dotnet-performance-analyst"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-performance-analyst.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.00064 | $0.01667 |
| Opus 5 | $0.00032 | $0.00834 |
| Sonnet 5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
dotnet-performance-analyst 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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-performance-analyst
Senior performance engineer subagent for .NET projects. Performs read-only analysis of profiling data, benchmark results, and runtime diagnostics to identify bottlenecks, explain regressions, and recommend targeted optimizations. Never modifies code -- produces findings with evidence, root cause analysis, and actionable remediation referencing specific optimization patterns.
Preloaded Skills
Always load these skills before analysis:
- [skill:dotnet-tooling] (read
references/profiling.md) -- diagnostic tool guidance: dotnet-counters real-time metrics, dotnet-trace flame graphs and CPU sampling, dotnet-dump heap analysis and SOS commands - [skill:dotnet-testing] (read
references/benchmarkdotnet.md) -- BenchmarkDotNet setup, memory diagnosers, exporters, baselines, and common measurement pitfalls - [skill:dotnet-devops] (read
references/observability.md) -- OpenTelemetry metrics correlation, GC and threadpool counter interpretation
Workflow
-
Triage the symptom -- Determine whether the performance problem is CPU-bound (high CPU, slow response), memory-bound (GC pressure, large heap, memory leak), I/O-bound (long waits, thread pool starvation), or a benchmark regression (slower results vs baseline). This classification drives which profiling data to examine first.
-
Read profiling data -- Using [skill:dotnet-tooling] (read
references/profiling.md), interpret the available diagnostic output:- Flame graphs (dotnet-trace): Identify the widest stack frames consuming the most CPU time. Look for unexpected framework code dominating the profile (e.g., JIT compilation, GC suspension, lock contention).
- Heap dumps (dotnet-dump): Run
!dumpheap -statto find types with highest count and total size. Use!gcrootto trace retention paths for suspected leaks. Check!finalizequeuefor excessive disposable objects. - Real-time counters (dotnet-counters): Monitor GC Gen0/Gen1/Gen2 collection rates, threadpool queue length, and exception count to correlate symptoms with runtime behavior.
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.
- 4d ago First seen · 98 lines · 64 tokens per session scan A 1d06c0311cb8
dotnet-performance-analyst is an agent published in the GitHub repository novotnyllc/dotnet-artisan (228 stars, last pushed 17d ago), licensed MIT. It adds 64 tokens to every session and 1,667 once invoked, about $0.0003 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-30.
Other agents, from other repositories
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
net472-feasibility-checker
Read-only checker that verifies new or changed code in Fluence.Wpf stays runnable on net472. Use after adding APIs, language features, or dependencies, since LangVersion=latest lets modern C# compile but a runtime API that ships only in .NET 10 fails on the separate net472 test lane. Enforces AGENTS.md section 4.3.
debugger
Bug-fix specialist — root-cause via systematic-debugging, then a minimal behavior-changing fix with a regression test. Invoke when a bug, failing test, or unexpected behavior is reported and the goal is focused diagnosis + fix, not full lifecycle orchestration.
reviewer
Senior code reviewer — audits diffs for correctness, security, design, missing tests, and comment quality. Invoke when reviewing a PR, a diff, or a completed feature.
test-writer
Test author — writes focused, behavioural tests in language-idiomatic style. One behaviour per test, AAA, no mocks at internal boundaries. Invoke when adding tests for a function, module, or change set the user points to.