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/skywinder/osm-edit-mcpWrote 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/skywinder/osm-edit-mcp/osm-development-safety)<a href="https://agentmods.dev/rules/skywinder/osm-edit-mcp/osm-development-safety"><img src="https://agentmods.dev/badge/rules/skywinder/osm-edit-mcp/osm-development-safety.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.01063 | $0.01063 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
osm-development-safety 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 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.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSM Development Safety and Best Practices
⚠️ CRITICAL: Always Ask Before Irreversible Operations
NEVER perform these operations without explicit user confirmation:
OpenStreetMap Write Operations
- Creating or closing changesets via OSM API
- Uploading nodes, ways, or relations to OSM
- Modifying existing OSM map data
- Deleting OSM elements
- Any calls to production
api.openstreetmap.orgendpoints
Configuration Safety
- Always use development API for testing:
OSM_USE_DEV_API=truein .env - Production API requires extreme caution:
OSM_USE_DEV_API=false - Never commit real OAuth credentials to version control
Development API Configuration
Safe Development Setup
# In .env file - ALWAYS use for development
OSM_USE_DEV_API=true
OSM_DEV_API_BASE=https://api06.dev.openstreetmap.org/api/0.6
Production API (Use with Extreme Caution)
# Only for production deployments
OSM_USE_DEV_API=false
OSM_API_BASE=https://api.openstreetmap.org/api/0.6
The server.py OSMConfig class automatically selects the correct API based on OSM_USE_DEV_API setting.
Testing Guidelines
Automated Testing
- Run test_comprehensive.py before any changes
- Expected results documented in TEST_RESULTS_SUMMARY.md
- Write operations will fail without OAuth (this is expected and safe)
Manual Testing Process
- Follow TESTING_CHECKLIST.md systematically
- Start with read operations (safe)
- Test configuration switching (dev/prod)
- Validate error handling
- Never test write operations on production without user consent
MCP Tool Implementation Patterns
Read Operations (Safe)
All tools in server.py that only retrieve data:
get_osm_node,get_osm_way,get_osm_relationfind_nearby_amenities,validate_coordinatesget_place_info,search_osm_elements
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 · 137 lines · 1,063 tokens per session scan A 1f68e60854cb
osm-development-safety is a cursor rule published in the GitHub repository skywinder/osm-edit-mcp (4 stars, last pushed yesterday), licensed MIT. It adds 1,063 tokens to every session, about $0.0053 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
mintlify
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.