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 instructions/attemainio/dotnet-toolkit/claude-mdgit 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/instructions/attemainio/dotnet-toolkit/claude-md)<a href="https://agentmods.dev/instructions/attemainio/dotnet-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/attemainio/dotnet-toolkit/claude-md.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.02493 | $0.02493 |
| Opus 5 | $0.01247 | $0.01247 |
| Sonnet 5 | $0.00499 | $0.00499 |
| Haiku 4.5 | $0.00249 | $0.00249 |
Grade A, and why
dotnet-toolkit CLAUDE.md 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in this repository. This file is the operating contract: the rules that apply in every session, plus where to read the detail. It is not the repo's manual — anything needed only for a particular kind of task lives behind a pointer below.
What this is
A Claude Code plugin for .NET repositories: a Roslyn-powered MCP server (DotnetToolkit.McpServer)
exposing token-efficient code query, project navigation, and development-log tools, plus skills that
teach Claude to prefer these tools over raw Read/Grep/dotnet build. This repo is both the plugin's
implementation and (via .mcp.json) a live consumer of its own server. Dogfooding is the point: if a
tool is awkward or wrong for a real task here, that's a bug report about the tool, not a reason to fall
back to shell.
Non-negotiable workflow
.claude/rules/dotnet-index.md is a router and nothing else: it names no tools, and maps an
intent (read C#, write C#, explore, review) to the skill that owns it. It is always-loaded alongside
this file, and is the same rule dotnet-init copies into consuming repos.
The protocol itself lives one level down, loaded only when the work needs it:
| Owns | File |
|---|---|
Every retrieval tool, what each answers, the cheap-route table, limitedBy, TOON |
skills/dotnet-read/SKILL.md |
validate_patch/rename_symbol, the fetch-to-patch loop, the standards step, failures |
skills/dotnet-write/SKILL.md |
Briefing and launching the dotnet-explore agent |
skills/dotnet-explore/SKILL.md |
Partitioning and launching dotnet-code-review |
skills/dotnet-review/SKILL.md |
| Which coding standard applies when — shared by the writer and the reviewer | standards/index.md |
None of it is repeated in CLAUDE.md: a rule that lives only here never reaches a consumer, and two
copies always diverge.
What this repo adds on top, because it is the plugin's own source tree:
Before finishing, run dotnet test and, if anything under src/ changed, re-publish to dist/
— dist/ is what actually runs, so a server change is not delivered until it is republished. dist/
now also carries the hooks, so a change under Hooks/ is live only after republishing too.
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.
- 3d ago First seen · 152 lines · 2,493 tokens per session scan A 8d9b45c4725e
dotnet-toolkit CLAUDE.md is an instructions file published in the GitHub repository Attemainio/dotnet-toolkit (2 stars, last pushed 7d ago), licensed MIT. It adds 2,493 tokens to every session, about $0.0125 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 instructions, from other repositories
vela-skill AGENTS.md
Instructions for dbhq-uk/vela-skill, covering agents.md, what this is, layout, the three constraints that define this tool and why razor works here and nowhere else.
csharp-lsp CLAUDE.md
Instructions for zircote/csharp-lsp, covering claude.md, project overview, setup, key files and conventions.
DotNetAnalyzer CLAUDE.md
Claude Code instructions for CartapenaBark/DotNetAnalyzer, covering claude.md, 常用命令, 构建和测试, 打包和安装 and mcp 服务器.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
moorestech AGENTS.md
AGENTS.md instructions for moorestech/moorestech, covering コーディングの指針, qa（必須）, 互換性とパフォーマンス, 既知の制約（設計上の割り切り） and regionの活用.
bitfinex-net
Use Bitfinex.Net when generating C#/.NET code that interacts with Bitfinex, including Spot, margin, derivatives symbols, funding, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on Bitfinex integration requests in C#, .NET, dotnet, F#, or VB.NET context.