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/bytedreamer/dotnetframeworkmcp/claude-mdgit clone --depth 1 https://github.com/bytedreamer/DotNetFrameworkMCPWhat 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.00617 | $0.00617 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
DotNetFrameworkMCP 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Development Guidelines
Project Information
This is a .NET Framework MCP (Model Context Protocol) server for Windows that enables building, testing, and running .NET Framework projects remotely.
Testing Framework
Use NUnit for all tests - This project uses NUnit, not xUnit or MSTest.
Test Structure:
using NUnit.Framework;
[TestFixture]
public class MyServiceTests
{
[SetUp]
public void SetUp()
{
// Initialize test dependencies
}
[TearDown]
public void TearDown()
{
// Cleanup resources
}
[Test]
public void MyMethod_WithValidInput_ReturnsExpectedResult()
{
// Arrange
// Act
// Assert
Assert.That(result, Is.EqualTo(expected));
}
[TestCase("value1", "expected1")]
[TestCase("value2", "expected2")]
public void MyMethod_WithDifferentInputs_ReturnsExpectedResults(string input, string expected)
{
// Test implementation
}
}
NUnit Assertions:
- Use
Assert.That(actual, Is.EqualTo(expected))instead ofAssert.Equal() - Use
Assert.That(collection, Has.Count.EqualTo(3))for collections - Use
Assert.That(text, Does.Contain("substring"))for string checks - Use
Times.Oncewith Moq for verifications
Build Commands
Development:
# Build the server
dotnet build src/DotNetFrameworkMCP.Server
# Run tests
dotnet test
# Run with dotnet CLI enabled
set MCPSERVER__UseDotNetCli=true
dotnet run --project src/DotNetFrameworkMCP.Server -- --port 3001
IMPORTANT: Pre-Commit Workflow
ALWAYS build and test before committing!
# 1. Build to ensure no compilation errors
dotnet build
# 2. Run tests to ensure functionality works
dotnet test
# 3. Only commit if both succeed
git add -A
git commit -m "Your commit message"
If build or tests fail, fix the issues before committing. Never commit broken code.
Production:
# Build self-contained executable
build-on-windows.bat
# Run the compiled executable
run-tcp-server.bat
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 · 109 lines · 617 tokens per session scan A a168188aa542
DotNetFrameworkMCP CLAUDE.md is an instructions file published in the GitHub repository bytedreamer/DotNetFrameworkMCP (23 stars, last pushed 1y ago), licensed Apache-2.0. It adds 617 tokens to every session, about $0.0031 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.