Borrowing it
Nothing to install: this file belongs to mathematic-inc/claude-tools-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/mathematic-inc/claude-tools-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/mathematic-inc/claude-tools-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/mathematic-inc/claude-tools-mcp/claude-md)<a href="https://agentmods.dev/instructions/mathematic-inc/claude-tools-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mathematic-inc/claude-tools-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.01200 | $0.01200 |
| Opus 5 | $0.00600 | $0.00600 |
| Sonnet 5 | $0.00240 | $0.00240 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
claude-tools-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 7d 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 — 157 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
This is an MCP (Model Context Protocol) server that exposes Claude Code's file and shell tools over HTTP, allowing other MCP clients to use these tools remotely. The server runs in stateless mode for horizontal scaling.
Development Commands
Building
go build -o claude-tools-mcp ./cmd/claude-tools-mcp
Running Tests
# Run all tests
go test ./...
# Run tests for a specific package
go test ./internal/tools
# Run a specific test
go test -run TestFunctionName ./internal/tools
Running the Server
# Default (localhost:8080)
go run ./cmd/claude-tools-mcp
# Custom address
go run ./cmd/claude-tools-mcp --addr localhost:9000
Releases
The project uses GoReleaser for automated releases.
Creating a Release
-
Tag a version: Create and push a git tag with semantic versioning:
git tag -a v0.1.0 -m "Release v0.1.0" git push origin v0.1.0 -
Automated build: GitHub Actions will automatically:
- Run tests
- Build binaries for multiple platforms (Linux, macOS, Windows on amd64/arm64)
- Create archives with checksums
- Generate changelog from commits
- Create a GitHub release with all artifacts
Local Testing
Test the release configuration locally without publishing:
# Install goreleaser (if not already installed)
go install github.com/goreleaser/goreleaser/v2@latest
# Test release build (no publishing)
goreleaser release --snapshot --clean
# Check what would be released
goreleaser check
Release Artifacts
Each release includes:
- Pre-built binaries for Linux, macOS, and Windows (amd64 and arm64)
- Compressed archives (tar.gz for Unix, zip for Windows)
- SHA256 checksums for verification
- Automatically generated changelog
Architecture
Core Components
cmd/claude-tools-mcp/main.go: HTTP server entrypoint
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.
- 7d ago First seen · 157 lines · 1,200 tokens per session scan A 24d36a7088d4
claude-tools-mcp CLAUDE.md is an instructions file published in the GitHub repository mathematic-inc/claude-tools-mcp (17 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,200 tokens to every session, about $0.0060 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
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.