Borrowing it
Nothing to install: this file belongs to jcucci/dotnet-sherlock-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jcucci/dotnet-sherlock-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/jcucci/dotnet-sherlock-mcpWrote 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/jcucci/dotnet-sherlock-mcp/agents-md)<a href="https://agentmods.dev/instructions/jcucci/dotnet-sherlock-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jcucci/dotnet-sherlock-mcp/agents-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.1 | $0.00760 | $0.00760 |
| Opus 5 | $0.00380 | $0.00380 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
dotnet-sherlock-mcp AGENTS.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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/Sherlock.MCP.slnx: Solution file (XML format).src/server: MCP server (Sherlock.MCP.Server) and entry point.src/runtime: Core analysis services and contracts (Sherlock.MCP.Runtime).src/unit-tests: xUnit tests (e.g.,MemberAnalysisServiceTests.cs).src/example: Minimal console example.src/docs: Roadmap and supporting docs.
Build, Test, and Development Commands
dotnet restore && dotnet build src/Sherlock.MCP.slnx: Restore and build (net9.0).dotnet run --project src/server/Sherlock.MCP.Server.csproj: Run MCP server over stdio.dotnet test src/unit-tests/Sherlock.MCP.Tests.csproj: Run unit tests.dotnet test --collect:"XPlat Code Coverage": Run tests with coverage (coverlet)../tool-install.sh/./tool-uninstall.sh: Pack and install/uninstall the global tool (sherlock-mcp).
Coding Style & Naming Conventions
- C# 12/.NET 9, nullable enabled, implicit usings on; prefer file‑scoped namespaces.
- Indentation: 4 spaces; wrap at ~120 chars where practical.
- Naming: PascalCase for types/methods/properties; camelCase for locals/parameters; interfaces start with
I. - Prefer expression-bodied members when clear; use named parameters when argument meaning isn’t obvious.
- Keep code self‑documenting; avoid redundant inline comments. Braces optional for single‑line blocks if readability holds.
Whitespace & Formatting
- Use a single blank line between the
usingblock and the file‑scopednamespace. - Use a single blank line after the file‑scoped
namespacebefore the first type/member. - Keep exactly one blank line between consecutive members inside a type (methods, properties, events, nested types) to separate logical units.
- Within longer methods, group related steps and separate them with a single blank line (setup, processing, return) — no multiple consecutive blank lines.
- Ensure files end with a trailing newline; avoid trailing whitespace on lines.
- Maintain one top‑level type per file; nested types are allowed within their parent file.
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.
- 8d ago First seen · 49 lines · 760 tokens per session scan A e5e262191ed8
dotnet-sherlock-mcp AGENTS.md is an instructions file published in the GitHub repository jcucci/dotnet-sherlock-mcp (7 stars, last pushed 1mo ago), licensed MIT. It adds 760 tokens to every session, about $0.0038 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.