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/pulsemcp/mcp-servers/agents-mdgit clone --depth 1 https://github.com/pulsemcp/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/pulsemcp/mcp-servers/agents-md)<a href="https://agentmods.dev/instructions/pulsemcp/mcp-servers/agents-md"><img src="https://agentmods.dev/badge/instructions/pulsemcp/mcp-servers/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.06669 | $0.06669 |
| Opus 5 | $0.03334 | $0.03334 |
| Sonnet 5 | $0.01334 | $0.01334 |
| Haiku 4.5 | $0.00667 | $0.00667 |
Grade C, and why
mcp-servers AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules How it starts
The opening of the file, as written. The whole thing — 521 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.
Also review CONTRIBUTING.md for context.
Repository Overview
This is a monorepo containing Model Context Protocol (MCP) servers built by PulseMCP. Each subfolder represents a standalone MCP server with its own functionality.
Repository Structure
productionized/: Directory for production-ready MCP serversexperimental/: Directory for experimental MCP servers in developmentlibs/mcp-server-template/: Template structure for creating new MCP servers
Git Workflow
- Repository:
https://github.com/pulsemcp/mcp-servers - Branch naming:
<github-username>/<feature-description>(e.g.,tadasant/fix-bug) - Main branch has CI/CD
- Always include test coverage for changes
- PRs should have concise titles and detailed descriptions using this format:
PR Description Format
This overrides the default Claude Code PR template. Do NOT use a ## Test plan section with unchecked checkboxes. Instead, use this format:
## Summary
<what changed and why>
## Verification
- [x] <what you actually did to verify this works>
- [x] <proof: concrete evidence it works — not just an assertion>
The ## Verification section documents how you closed the loop — what you actually did, not what should be done. Every checkbox must be checked before the PR is opened. If you can't verify something, explain why instead of leaving an unchecked box.
Proof: Show, Don't Tell
Every verification item should include proof — concrete evidence that the change works. "Tested it and it works" is NOT proof. A screenshot, a test output, or a confirmation receipt IS proof.
Proof types and when to use them:
- E2E test report — For backend/logic changes. Describe what you tested end-to-end and what happened. This is the most common type.
- Screenshot — For UI changes. UI changes MUST include screenshots. No exceptions.
- External confirmation — For tasks with external side effects (API calls, emails sent, deployments). Show the confirmation or response.
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 · 521 lines · 6,669 tokens per session scan C 97e6e609722f
mcp-servers AGENTS.md is an instructions file published in the GitHub repository pulsemcp/mcp-servers (80 stars, last pushed 4d ago), licensed MIT. It adds 6,669 tokens to every session, about $0.0333 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.