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/testing-and-qualitygit 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/testing-and-quality)<a href="https://agentmods.dev/rules/skywinder/osm-edit-mcp/testing-and-quality"><img src="https://agentmods.dev/badge/rules/skywinder/osm-edit-mcp/testing-and-quality.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 | $0.00000 | $0.01707 |
| Opus 5 | $0.00000 | $0.00853 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
testing-and-quality 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 4d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing and Quality Assurance Guide
Comprehensive Testing Framework
Automated Testing with test_comprehensive.py
The test_comprehensive.py provides systematic testing of all 31 MCP tools:
# Run full test suite
python test_comprehensive.py
# Expected output: JSON report, logs, and console summary
Test Categories
- Read Operations (Tests 1-15): Safe operations that should mostly pass
- Write Operations (Tests 16-27): OAuth-protected, expected to fail without auth
- Natural Language (Tests 28-31): Input validation and processing
Manual Testing with TESTING_CHECKLIST.md
Follow TESTING_CHECKLIST.md for systematic manual validation:
Testing Phases
- Pre-test Setup: Configuration verification
- Automated Testing: Run comprehensive test suite
- Manual Testing: Phase-by-phase validation
- Configuration Testing: Dev/prod switching
- Error Handling: Edge cases and failures
- Performance Testing: Response times and memory
- Security Testing: Credential handling and validation
Test Results Analysis
Review TEST_RESULTS_SUMMARY.md for:
- ✅ Working tools (ready for use)
- ❌ Expected failures (OAuth-dependent, normal)
- 🔧 Issues to debug (actual problems requiring fixes)
Quality Standards
Test Success Criteria
- Read operations: ≥80% success rate
- Write operations: Expected 401/auth failures
- Validation tools: 100% success rate
- Error handling: Graceful failures with informative messages
Configuration Testing
Test dev/prod switching in .env:
# Test development mode
OSM_USE_DEV_API=true
python -c "from src.osm_edit_mcp.server import config; print(config.current_api_base_url)"
# Test production mode (careful!)
OSM_USE_DEV_API=false
python -c "from src.osm_edit_mcp.server import config; print(config.current_api_base_url)"
Logging Level Testing
Verify log levels in .env:
LOG_LEVEL=DEBUG # Should show detailed debug info
LOG_LEVEL=INFO # Should show operation info
LOG_LEVEL=WARNING # Should show only warnings/errors
LOG_LEVEL=ERROR # Should show only errors
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.
- 4d ago First seen · 226 lines · 0 tokens per session scan A 9a10cd69c43e
testing-and-quality is a cursor rule published in the GitHub repository skywinder/osm-edit-mcp (4 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,707 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.