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/jbeshir/mcp-servers/claude-mdgit clone --depth 1 https://github.com/jbeshir/mcp-serversWrote 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/jbeshir/mcp-servers/claude-md)<a href="https://agentmods.dev/instructions/jbeshir/mcp-servers/claude-md"><img src="https://agentmods.dev/badge/instructions/jbeshir/mcp-servers/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.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
mcp-servers 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - mcp-servers (Go workspace)
Project Structure
This is a Go workspace containing multiple MCP (Model Context Protocol) servers. Each server lives in its own module subdirectory and is listed in go.work.
Validation
To validate changes in this repository, run the following automated checks:
- Linting:
make lint - Tests:
make test-short - Build all servers:
make build
All automated steps must pass before changes can be merged.
For changes to datasource scraping/parsing logic, also run live integration tests:
- Integration tests:
make test(omits-short— hits live supermarket sites, may be flaky)
Additionally, perform global manual quality checks, plus these project-specific checks:
- Environment variables: Check that env vars referenced in code are documented in the server's README.
- MCP tool definitions in sync: When changing tools, check all three locations are consistent:
internal/server/tools.go— authoritative tool registration (descriptions, parameters, options)manifest.json— tool list for MCPB distribution (every server must have one)README.md— user-facing tool documentation table
- server.json descriptions: Must be ≤100 characters (MCP registry rejects longer ones).
All steps must pass before changes can be merged.
Desloppify
Subjective LLM-based code review complementing golangci-lint. Local-only (not in CI).
make desloppify— scan for quality issuesdesloppify next— show priority fix queue.desloppify/is committed for state persistence across sessions- Exclude worktree directories when created:
desloppify exclude <worktree-dir>/
Coding Standards
Datasource Constructors
- Per-store wrappers (e.g.
NewHiyou) are thin: fill in the store-specificConfigand delegate to the generic constructor
Mocks (assets module)
assets/internal/assetcore/mocks/ contains generated mocks (via mockery) of the IconProvider, IllustrationProvider, and FontProvider interfaces from assets/internal/assetcore/provider.go. These files carry a // Code generated by mockery. DO NOT EDIT. header — never hand-edit them; change the source interface and regenerate instead.
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.
- 5d ago First seen · 58 lines · 654 tokens per session scan A acc3aabe0fef
mcp-servers CLAUDE.md is an instructions file published in the GitHub repository jbeshir/mcp-servers (1 stars, last pushed 1mo ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 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).
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.