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/webdevtodayjason/slim-mcp/claude-mdgit clone --depth 1 https://github.com/webdevtodayjason/slim-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/webdevtodayjason/slim-mcp/claude-md)<a href="https://agentmods.dev/instructions/webdevtodayjason/slim-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/webdevtodayjason/slim-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 | $0.00322 | $0.00322 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
slim-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 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.
What it actually says
Claude Tools Project Guide
Environment Setup & Run Commands
# Create conda environment with Python 3.11
conda create -n mcp-tools python=3.11
# Activate environment
conda activate mcp-tools
# Install with uv (preferred)
uv pip install -e .
# Alternative: Install with pip
pip install -e .
# Run the application
python -m claude_tools.main
Configuration
Claude Config
{
"mcpServers": {
"claude-tools": {
"command": "/Users/jasonbrashear/miniconda3/envs/claude-tools/bin/python",
"args": ["-m", "claude_tools.main"]
}
}
}
Cursor Config
NAME: claude-tools
TYPE: command
COMMAND: /Users/jasonbrashear/miniconda3/envs/claude-tools/bin/python -m claude_tools.main
Code Style Guidelines
- Follow PEP 8 conventions
- Use Google-style docstrings for functions and classes
- Type annotations required for all function parameters and return values
- Constants defined at module level in UPPER_CASE
- Imports ordered: standard library, third-party, local
- Error handling: use try/except blocks with specific exceptions
- Function names use snake_case
- Class names use PascalCase
- Prefer async/await for I/O operations
- Each tool function should have a clear single responsibility
- Use meaningful variable names that describe purpose
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 · 52 lines · 322 tokens per session scan A c5f223736e2c
slim-MCP CLAUDE.md is an instructions file published in the GitHub repository webdevtodayjason/slim-MCP (1 stars, last pushed 1y ago), licensed MIT. It adds 322 tokens to every session, about $0.0016 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
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.