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-edit-safety)<a href="https://agentmods.dev/rules/skywinder/osm-edit-mcp/osm-edit-safety"><img src="https://agentmods.dev/badge/rules/skywinder/osm-edit-mcp/osm-edit-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.00815 | $0.00815 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
osm-edit-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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSM Edit MCP Server - Safety and Development Rules
⚠️ CRITICAL: Ask Before Irreversible Operations
ALWAYS ask the user before performing these irreversible operations:
OpenStreetMap Operations
- Creating or closing changesets via OSM API
- Uploading nodes, ways, or relations to OSM
- Modifying existing OSM map data
- Deleting OSM elements
- Making any calls to
api.openstreetmap.orgendpoints that modify data - Testing with real OSM data (suggest using dev.openstreetmap.org instead)
Authentication & Credentials
- Revoking or modifying OAuth tokens
- Changing OAuth application settings
- Exposing credentials in code or commits
- Modifying .env file with real credentials
Repository Operations
- Force pushing to git repository
- Deleting git history or branches
- Publishing package to PyPI
- Creating GitHub releases
Project Structure
Core Files
- src/osm_edit_mcp/server.py - Main server and
osm-edit-mcpentry point - pyproject.toml - Package configuration and dependencies
Configuration
- .env - NEVER commit - Contains real OAuth credentials
- .env.example - Template for environment variables
- .gitignore - Protects sensitive files from git
Documentation
- README.md - Comprehensive setup and usage guide
Development Safety Guidelines
1. Testing Environment
- ALWAYS use
dev.openstreetmap.orgfor testing, not production API - Set
OSM_USE_DEV_API=trueand use the allowlisted development target - Verify API base URL before any write operations
2. OAuth Security
- Keep client secrets in .env file only
- Use keyring for persistent token storage
- Reauthorize expired tokens without exposing callback URLs or token data
- Never log full OAuth tokens
3. Error Handling
- Implement comprehensive error handling for OSM API responses
- Validate all input data before sending to OSM
- Handle rate limiting (max 10,000 API calls per hour)
- Gracefully handle network failures
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.
- 3d ago Changed · -2 lines · -27 tokens per session 032ac0e8b415
- 8d ago First seen · 106 lines · 842 tokens per session scan A 6636152bd864
osm-edit-safety is a cursor rule published in the GitHub repository skywinder/osm-edit-mcp (4 stars, last pushed today), licensed MIT. It adds 815 tokens to every session, about $0.0041 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-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.