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/sfc-gh-cconner/support-rules-mcp/13-testing-standardsgit clone --depth 1 https://github.com/sfc-gh-cconner/support-rules-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/sfc-gh-cconner/support-rules-mcp/13-testing-standards)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/13-testing-standards"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/13-testing-standards.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.01726 | $0.01726 |
| Opus 5 | $0.00863 | $0.00863 |
| Sonnet 5 | $0.00345 | $0.00345 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
13-testing-standards 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 5d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing & Quality Standards
PURPOSE: Testing requirements and quality standards for rule validation.
🧪 Testing Requirements
Mandatory Testing
- All new rules must include working examples
- Code snippets must be tested before committing
- Query patterns must be validated against Snowhouse
- MCP tool examples must be verified
Test Coverage Standards
- Test both success and failure scenarios
- Include edge cases and boundary conditions
- Document complex test scenarios
- Validate examples work in real environments
Testing Framework for Rules
# Validate rule syntax and structure
python scripts/validate_rules.py
# Test MCP server can load all rules
python server_proper.py --validate
# Check rule examples
python scripts/test_rule_examples.py rules/core/06-snowflake-cli.mdc
🚨 Deployment Blockers
CRITICAL TESTING RULES
- CRITICAL: NEVER RELEASE WITH FAILING VALIDATION - All rules must be valid
- ABSOLUTE RULE: NO SKIP-VALIDATION OPTION - Validation is mandatory
- DEPLOYMENT BLOCKER: Invalid rules prevent deployment - Fix all errors before release
Validation Execution
# Run full validation suite
python scripts/validate_all_rules.py
# Validate specific directory
python scripts/validate_rules.py rules/core/
# Check cross-references
python scripts/check_rule_references.py
📊 Quality Metrics
Rule Quality Requirements
- All rules must have clear PURPOSE statements
- Examples must be tested and work correctly
- Cross-references must be accurate
- Markdown must be properly formatted
- No broken links or references
Rule Development Testing
When creating rules:
- Include examples for common use cases
- Test CLI commands and output
- Validate SQL queries against Snowhouse
- Test cross-platform compatibility (if applicable)
- Verify MCP tool calls work as documented
🔧 Test Organization
Test Structure
scripts/
├── validate_rules.py # Rule syntax validation
├── test_rule_examples.py # Example code testing
├── check_references.py # Cross-reference validation
└── lint_markdown.py # Markdown linting
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.
- 5d ago First seen · 280 lines · 1,726 tokens per session scan A 6b41bdcae903
13-testing-standards is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 1,726 tokens to every session, about $0.0086 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.