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/Kenlan2022/mcp_servers_showcaseWrote 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/kenlan2022/mcp_servers_showcase/global-standards)<a href="https://agentmods.dev/rules/kenlan2022/mcp_servers_showcase/global-standards"><img src="https://agentmods.dev/badge/rules/kenlan2022/mcp_servers_showcase/global-standards.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.01898 | $0.01898 |
| Opus 5 | $0.00949 | $0.00949 |
| Sonnet 5 | $0.00380 | $0.00380 |
| Haiku 4.5 | $0.00190 | $0.00190 |
Grade A, and why
global-standards 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
type: always name: "Global MCP Standards" description: "Common standards for all MCP servers with incremental development approach"
Global MCP Server Development Standards
Core Philosophy: Incremental Development
CRITICAL: Never create multiple untested files at once. Follow the incremental approach:
- Plan First: Always create or update TODO/TASKS lists before coding
- One Step at a Time: Implement one feature/component at a time
- Test Immediately: Write and run tests for each component before moving to next
- Document Progress: Update TODO lists and add completion notes
- Review Before Proceed: Ensure current step works before starting next
Project Structure Requirements
Use UV for Development
# Project initialization
uv init mcp-servers-project
cd mcp-servers-project
uv add mcp fastapi uvicorn pytest pytest-asyncio
# Development dependencies
uv add --dev black isort mypy flake8 pre-commit
Task Management (MANDATORY)
Before any coding, create/update:
TODO.md Example:
# TODO List
## Current Sprint
- [ ] Setup basic MCP server structure
- [ ] Implement ping/pong handler
- [ ] Add basic tool registration
- [ ] Write unit tests for handlers
## Completed
- [x] Project initialization with UV
- [x] Basic project structure setup
## Blocked/Questions
- [ ] Need to research MCP protocol version compatibility
TASKS.md Example:
# Detailed Task Breakdown
## Task: Setup Basic MCP Server Structure
**Status**: In Progress
**Priority**: High
### Subtasks:
1. [x] Create main.py with MCP server initialization
2. [ ] Add configuration management
3. [ ] Implement basic logging
4. [ ] Add error handling middleware
### Acceptance Criteria:
- Server can start without errors
- Basic logging is working
- Configuration can be loaded from environment
### Notes:
- Using uvicorn for ASGI server
- MCP protocol requires specific message format
Development Workflow
Incremental Implementation Steps
Step 1: Always Plan
# Before implementing, add TODO comments
# TODO: Implement MCP server initialization
# TODO: Add message handler registration
# TODO: Implement basic error handling
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 · 321 lines · 1,898 tokens per session scan A 5c2fadefd436
global-standards is a cursor rule published in the GitHub repository Kenlan2022/mcp_servers_showcase (0 stars, last pushed 1y ago), licensed MIT. It adds 1,898 tokens to every session, about $0.0095 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 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.