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.
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers)<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.04511 |
| Opus 5 | $0.00009 | $0.02256 |
| Sonnet 5 | $0.00003 | $0.00902 |
| Haiku 4.5 | $0.00002 | $0.00451 |
Grade C, and why
510-mcp-servers 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
if any(dangerous in command for dangerous in ['rm -rf', '> /dev/', '|', ';']): How it starts
The opening of the file, as written. The whole thing — 702 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Engineering Ruleset
Goal: Build MCP servers with rich, AI-agent-friendly documentation that enables effective tool selection and usage.
About MCP
The Model Context Protocol (MCP) is a vendor-neutral, open standard managed by the Linux Foundation's Agentic AI Foundation. MCP enables consistent AI agent integration across platforms (Claude Code, Cursor, GitHub Copilot, and others), solving the n×m integration problem where every AI client had to integrate separately with every tool.
Key Capabilities:
- Multi-vendor: GitHub, Microsoft, OpenAI, Anthropic, community-supported
- Enterprise-ready: OAuth for remote servers, no proprietary tokens
- Long-running tasks: Support for builds, deployments, multi-minute operations
- Discoverable: MCP Registry for governance and discoverability
- Production-grade: Industry-standard maturity (like Kubernetes, GraphQL)
Core Principle
Exception to lean comment rules: MCP tools require detailed docstrings because AI agents rely on them for tool selection and usage. Unlike human-facing code, agents need rich descriptions to understand capabilities and constraints. This is critical for vendor-neutral AI agent ecosystems.
Tool Documentation Standards
Docstring Structure
MCP tool docstrings serve as API documentation for AI agents. They must be comprehensive:
@mcp.tool
async def kubectl(args: str) -> str:
"""Execute kubectl commands for Kubernetes cluster management.
Use this tool for all kubectl operations. Provide the kubectl
arguments as a single string (e.g., "get pods -n default").
**Important:** This tool requires kubectl to be installed and
configured with cluster access. Commands are executed with the
current user's kubeconfig context.
Args:
args: kubectl command arguments as a single string.
Examples:
- "get pods -n default"
- "apply -f deployment.yaml"
- "logs pod-name -n namespace --tail=100"
Returns:
JSON string with structure:
{
"stdout": "command output",
"stderr": "error output (empty if success)",
"statusCode": 0
}
Status codes:
- 0: Success
- 1: General error
- 2: Misuse of command
Raises:
RuntimeError: If kubectl is not installed or not in PATH
Example:
>>> result = await kubectl("get pods -n default")
>>> data = json.loads(result)
>>> print(data["stdout"])
NAME READY STATUS RESTARTS AGE
pod-123 1/1 Running 0 5m
"""
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 · 702 lines · 17 tokens per session scan C 13fae2e5a397
510-mcp-servers is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (17 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 4,511 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.