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 Attemainio/dotnet-toolkit --skill dotnet-reviewgit clone --depth 1 https://github.com/Attemainio/dotnet-toolkitWrote 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/attemainio/dotnet-toolkit/dotnet-review)<a href="https://agentmods.dev/skills/attemainio/dotnet-toolkit/dotnet-review"><img src="https://agentmods.dev/badge/skills/attemainio/dotnet-toolkit/dotnet-review/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.
<a href="https://agentmods.dev/skills/attemainio/dotnet-toolkit/dotnet-review"><img src="https://agentmods.dev/badge/skills/attemainio/dotnet-toolkit/dotnet-review.svg" alt="Reviewed on agentmods" width="80" 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.00218 | $0.02582 |
| Opus 5.5 | $0.00087 | $0.01033 |
| Sonnet 5.5 | $0.00044 | $0.00516 |
| Haiku 4.5 | $0.00022 | $0.00258 |
Grade A, and why
dotnet-review 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegating to dotnet-code-review
This plugin ships one review subagent, dotnet-code-review. Each invocation reviews all quality
aspects at once — correctness, naming, styling, best practices, performance, concurrency, security,
testing, XML documentation, cleanup/duplication — over one stated scope. It starts with no prior
context of the project: it reads code and the shared standards under the plugin's standards/
fresh, like a senior developer seeing the
codebase for the first time, and reports findings without editing anything. Route review requests to it
instead of reviewing inline yourself — it reads the actual standards files, which you have not loaded.
Host adapter
Claude Code can launch the bundled dotnet-code-review custom agent directly. Codex plugins do not
currently install custom-agent registrations. In Codex, launch the built-in read-only explorer and
start its brief with: "Read <pluginRoot>/agents/dotnet-code-review.md and follow its Markdown body;
ignore only the Claude-specific YAML frontmatter." The canonical brief stays under agents/; do not
duplicate it in a Codex wrapper.
Step 0 — check workspace readiness before launching
Call workspace_status yourself, before spawning anything. Each instance starts cold and cannot
fix a broken workspace; launching several against one is a parallel waste, not a parallel review.
workspace: degraded, or projects underfailed:— semantic results may be silently wrong, not merely thin. A review run against it reports findings it cannot stand behind. Fix the build,reload_workspace, then spawn.- Still loading, or index-only —
get_references,get_call_hierarchy,get_type_hierarchyandget_semantic_diffreturn nothing rather than nothing-found, and the classic failure is an instance reporting live code as dead. Wait for it. - After a
git checkout/pull/rebase, or a new or deleted.csfile —reload_workspace(scope: "all")first, or every instance's line numbers are wrong. - Take
pluginRootfrom the same response and state it in each instance's brief, so no instance has to rediscover where the standards live.
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.
- 1mo ago Changed · -1 lines 98fc2178c3a8
- 1mo ago Changed · +19 lines · +218 tokens per session 05625c12790c
- 1mo ago First seen · 148 lines · 0 tokens per session scan A 8fc9bda7063c
dotnet-review is a skill published in the GitHub repository Attemainio/dotnet-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 218 tokens to every session and 2,582 once invoked, about $0.0009 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.
Other skills, from other repositories
resharper-clt
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…
roslynator
Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…
stylecop-analyzers
Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…
dotnet-best-practices
Ensure .NET/C# code follows maintainable, modern best practices. Use when reviewing or improving C# code, solution structure, async patterns, dependency injection, or testability.
cratis-engineering-csharp-conventions
Apply the Cratis C# house conventions when writing or reviewing C# in a Cratis repository - formatting, naming, records and primary constructors, nullable handling, XML documentation, custom exceptions, structured logging, dependency injection, and service lifetimes. Use for any "how should this be written" C# style…
quickdup
Use the open-source free QuickDup clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring candidates, or repeatable duplication. USE FOR: the repo wants QuickDup; the team needs repeatable duplicate-code scans for C#; the user asks about DRY…