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/dave-hillier/refactor-mcp/agents-mdgit clone --depth 1 https://github.com/dave-hillier/refactor-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/dave-hillier/refactor-mcp/agents-md)<a href="https://agentmods.dev/instructions/dave-hillier/refactor-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dave-hillier/refactor-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 | $0.01011 | $0.01011 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
refactor-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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring MCP Server Contribution Guide
1. Big Picture
| Layer | What It Does | Where To Learn More |
|---|---|---|
| MCP Server | Hosts “tools”, “resources”, and “prompts” that the client (human or LLM) can call. | MCP C# SDK README → Getting Started (Server) section. |
| Refactoring Logic (Roslyn) | Analysers, code‑fixes and syntax transforms that change or inspect code safely. | Roslyn SDK quick‑starts and samples. |
MCP gives us the protocol surface; Roslyn gives us the ability to understand and rewrite C#; everything else is standard .NET hosting.
2. Key MCP Concepts (30‑second refresher)
| Concept | What It Represents | Typical Use in This Repo |
|---|---|---|
Tool ([McpServerTool]) |
A side‑effect‑free operation that returns something (e.g., “Extract Method”). | Main refactoring entry‑points. |
Resource ([McpServerResource]) |
Read‑only contextual data, addressable via URI templates. | Metrics, dependency graphs. |
Prompt ([McpServerPrompt]) |
A templated ChatMessage that instructs an LLM. |
Enforce architectural or style constraints. |
Tip: One class → one concept. Mixing tools and resources in the same type hurts discoverability.
3. Fast Path: Creating a New Refactoring Tool
- Decorate the class with
[McpServerToolType]and the method with[McpServerTool]. - Keep the surface minimal
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 · 82 lines · 1,011 tokens per session scan A e51783e30da2
refactor-mcp AGENTS.md is an instructions file published in the GitHub repository dave-hillier/refactor-mcp (92 stars, last pushed 2mo ago), licensed MPL-2.0. It adds 1,011 tokens to every session, about $0.0051 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.