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/codewithmukesh/dotnet-claude-kit/claude-mdgit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWrote 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/codewithmukesh/dotnet-claude-kit/claude-md)<a href="https://agentmods.dev/instructions/codewithmukesh/dotnet-claude-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/codewithmukesh/dotnet-claude-kit/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.02345 | $0.02345 |
| Opus 5 | $0.01172 | $0.01172 |
| Sonnet 5 | $0.00469 | $0.00469 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
dotnet-claude-kit 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 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-claude-kit — Development Instructions
These instructions are for developing THIS repository. For user-facing project templates, see
templates/.
Repository Purpose
dotnet-claude-kit is an opinionated Claude Code companion for .NET developers. It provides skills, agents, templates, knowledge documents, and a Roslyn MCP server that make Claude Code dramatically more effective for .NET development.
Philosophy
- Guided over prescriptive — We ask the right questions, then recommend the best approach with clear rationale
- Modern .NET only — Target .NET 10 and C# 14. No legacy patterns, no backwards compatibility with .NET Framework
- Architecture-aware — We support VSA, Clean Architecture, DDD, and Modular Monolith with an advisor skill that recommends the best fit (see ADR-005)
- Token-conscious — Every file respects context window limits. Skills max at 400 lines
- Practical over theoretical — Every recommendation includes a code example and a "why"
Skill Structure
Skills follow the Agent Skills open standard. Each skill lives at skills/<skill-name>/SKILL.md.
Frontmatter Schema (Required)
---
name: skill-name # kebab-case, matches directory name
description: >
What this skill does and when Claude should load it.
Include trigger keywords and specific scenarios.
---
Required Sections
- Core Principles — 3-5 numbered, opinionated defaults with rationale
- Patterns — Code examples with explanation. Each pattern has:
- A descriptive heading
- Working C# code (must compile conceptually)
- Brief explanation of why this is the recommended approach
- Anti-patterns — What NOT to do, with BAD/GOOD code comparison
- Decision Guide — Markdown table: Scenario → Recommendation
Quality Standards
- Maximum 400 lines — Every line must earn its place. Respect token budgets.
- Every recommendation has a "why" — No bare rules without justification
- Code examples must be modern C# — Primary constructors, collection expressions, file-scoped namespaces, records
- No Swashbuckle — Use built-in .NET OpenAPI support
- No repository pattern over EF Core — Use DbContext directly
TimeProvideroverDateTime.Now— Always
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 · 227 lines · 2,345 tokens per session scan A b07b4268997a
dotnet-claude-kit CLAUDE.md is an instructions file published in the GitHub repository codewithmukesh/dotnet-claude-kit (693 stars, last pushed 28d ago), licensed MIT. It adds 2,345 tokens to every session, about $0.0117 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.