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 rules/skywinder/osm-edit-mcp/mcp-implementation-patternsgit clone --depth 1 https://github.com/skywinder/osm-edit-mcpWhat 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.00000 | $0.01693 |
| Opus 5 | $0.00000 | $0.00847 |
| Sonnet 5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
mcp-implementation-patterns 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 2d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Implementation Patterns for OSM Server
FastMCP Server Structure
The server.py uses FastMCP framework with this pattern:
from mcp.server.fastmcp import FastMCP
# Initialize server
mcp = FastMCP("osm-edit-mcp")
# Define tools with decorator
@mcp.tool()
async def tool_name(param: type) -> Dict[str, Any]:
"""Tool description for AI assistant."""
# Implementation
MCP Tool Categories
1. Read Operations (Safe)
Tools that only retrieve data from OSM:
get_osm_node,get_osm_way,get_osm_relationget_osm_elements_in_area,get_changeset_historyfind_nearby_amenities,search_osm_elements
2. Validation and Utility Tools
Non-destructive operations for data validation:
validate_coordinates,validate_osm_dataget_place_info,smart_geocodeget_server_info,export_osm_data
3. Write Operations (OAuth Required)
Tools that modify OSM data:
create_osm_node,update_osm_node,delete_osm_nodecreate_osm_way,update_osm_way,delete_osm_waycreate_osm_relation,update_osm_relation,delete_osm_relationcreate_changeset,close_changeset
4. Natural Language Processing
Advanced tools for natural language interaction:
parse_natural_language_osm_requestcreate_place_from_descriptionfind_and_update_place,delete_place_from_descriptionbulk_create_places
Tool Implementation Pattern
Standard Tool Structure
@mcp.tool()
async def tool_name(param1: type, param2: Optional[type] = None) -> Dict[str, Any]:
"""Clear description of what the tool does.
Args:
param1: Description of required parameter
param2: Description of optional parameter
Returns:
Dictionary containing result data and status
"""
try:
# Log the operation
logger.debug(f"Operation description with params")
# Validate inputs
if not validate_input(param1):
return {
"success": False,
"error": "Validation error message",
"message": "Human-readable error"
}
# Build API URL using configuration
url = f"{config.current_api_base_url}/endpoint"
# Make API call
async with httpx.AsyncClient() as client:
response = await client.get(url)
response.raise_for_status()
# Process response
result_data = process_response(response)
return {
"success": True,
"data": result_data,
"message": "Success message"
}
except Exception as e:
logger.error(f"Tool failed: {str(e)}")
return {
"success": False,
"error": str(e),
"message": f"Failed to perform operation"
}
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.
- 2d ago First seen · 258 lines · 0 tokens per session scan A a9fb3667dac1
mcp-implementation-patterns is a cursor rule published in the GitHub repository skywinder/osm-edit-mcp (4 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,693 tokens. 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.