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/configuration-managementgit 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/configuration-management)<a href="https://agentmods.dev/rules/skywinder/osm-edit-mcp/configuration-management"><img src="https://agentmods.dev/badge/rules/skywinder/osm-edit-mcp/configuration-management.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.01631 | $0.01631 |
| Opus 5 | $0.00816 | $0.00816 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
configuration-management 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 yesterday.
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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Management System
Environment Configuration Files
Primary Configuration Files
- .env - Active environment configuration (never commit with real credentials)
- .env.example - Configuration template with all options documented
Configuration Class
The OSMConfig class in config.py uses Pydantic BaseSettings for type-safe configuration management.
Core Configuration Sections
API Configuration (Dev/Prod Switching)
# Safe development testing (default)
OSM_USE_DEV_API=true
OSM_DEV_API_BASE=https://api06.dev.openstreetmap.org/api/0.6
# Production use (requires extreme caution)
OSM_USE_DEV_API=false
OSM_API_BASE=https://api.openstreetmap.org/api/0.6
# Legacy support (will be deprecated)
OSM_API_BASE_URL=https://api06.dev.openstreetmap.org/api/0.6
OAuth 2.0 Credentials
OSM_DEV_CLIENT_ID=your_development_oauth_client_id
OSM_DEV_CLIENT_SECRET=your_development_oauth_client_secret
OSM_DEV_REDIRECT_URI=https://localhost:8080/callback
OSM_PROD_CLIENT_ID=your_production_oauth_client_id
OSM_PROD_CLIENT_SECRET=your_production_oauth_client_secret
OSM_PROD_REDIRECT_URI=https://localhost:8080/callback
Logging Configuration
LOG_LEVEL=INFO # DEBUG, INFO, WARNING, ERROR
DEBUG=false # Enable debug mode
DEVELOPMENT_MODE=false # Enable development features
Safety and Rate Limiting
REQUIRE_USER_CONFIRMATION=true # Require confirmation for destructive ops
RATE_LIMIT_PER_MINUTE=60 # API calls per minute
MAX_CHANGESET_SIZE=50 # Maximum operations per changeset
Cache Configuration
ENABLE_CACHE=true # Enable response caching
CACHE_TTL_SECONDS=300 # Cache expiration time
Security Settings
USE_KEYRING=true # Use system keyring for credentials
Configuration Usage Patterns
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.
- yesterday Changed · +3 lines · +48 tokens per session 1a1da81dee11
- 6d ago First seen · 227 lines · 1,583 tokens per session scan A 3dec9d5fb71b
configuration-management is a cursor rule published in the GitHub repository skywinder/osm-edit-mcp (4 stars, last pushed yesterday), licensed MIT. It adds 1,631 tokens to every session, about $0.0082 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.