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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/dave-hillier/refactor-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/dave-hillier/refactor-mcp/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.1 | $0.00801 | $0.00801 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
refactor-mcp 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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
RefactorMCP is a Model Context Protocol server that exposes Roslyn-based refactoring tools for C#. It provides extensive code transformation capabilities through both CLI and MCP server modes.
Architecture
Core Components
-
RefactorMCP.ConsoleApp: Main application hosting refactoring tools and MCP server
Tools/: Individual refactoring tool implementations (40+ tools)SyntaxRewriters/: Roslyn syntax tree rewriting componentsSyntaxWalkers/: Code analysis and traversal utilitiesMove/: Specialized method moving logic
-
RefactorMCP.Tests: Comprehensive xUnit test suite
- Each tool has corresponding test coverage
- Tests organized by feature area
Key Technologies
- .NET 9.0
- Roslyn (Microsoft.CodeAnalysis) for C# code analysis and transformation
- xUnit for testing
- Model Context Protocol for server functionality
Development Commands
Build
dotnet build
Run Tests
# Run all tests
dotnet test
# Run tests with filter
dotnet test --filter "FullyQualifiedName~MoveInstanceMethod"
# Run a specific test
dotnet test --filter "FullyQualifiedName=RefactorMCP.Tests.Tools.MoveInstanceMethodTests.Move_MethodWithNamedArguments_Success"
Run Application
# Run MCP server
dotnet run --project RefactorMCP.ConsoleApp
# Run with JSON mode
dotnet run --project RefactorMCP.ConsoleApp -- --json <tool-name> '<json-params>'
# Example: Load solution
dotnet run --project RefactorMCP.ConsoleApp -- --json load-solution '{"solutionPath":"./RefactorMCP.sln"}'
Format Code
dotnet format
Working with Refactoring Tools
Tool Naming Convention
- Tools use kebab-case names (e.g.,
extract-method,move-instance-method) - Each tool has a corresponding class in
RefactorMCP.ConsoleApp/Tools/
Adding New Tools
- Create tool class in
RefactorMCP.ConsoleApp/Tools/ - Implement the refactoring logic using Roslyn APIs
- Add corresponding tests in
RefactorMCP.Tests/Tools/orRefactorMCP.Tests/ToolsNew/ - Register the tool in the appropriate location for MCP discovery
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.
- 6d ago First seen · 112 lines · 801 tokens per session scan A afa0077e6cdb
refactor-mcp CLAUDE.md is an instructions file published in the GitHub repository dave-hillier/refactor-mcp (93 stars, last pushed 2mo ago), licensed MPL-2.0. It adds 801 tokens to every session, about $0.0040 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).
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 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.
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.