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/cartaorobbin/pyramid-mcp/test-patternsgit clone --depth 1 https://github.com/cartaorobbin/pyramid-mcpWhat 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.01211 | $0.01211 |
| Opus 5 | $0.00606 | $0.00606 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
test-patterns 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 2d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unified Pyramid Fixture Pattern for Tests
🎯 Use the Unified pyramid_app Fixture
ALWAYS use the unified pyramid_app fixture for new tests. This is the single, standardized way to create Pyramid applications in tests.
1. Basic Test Pattern
def test_basic_functionality(pyramid_app):
"""Use pyramid_app directly with defaults."""
app = pyramid_app()
response = app.post_json('/mcp', {
'jsonrpc': '2.0',
'id': 1,
'method': 'tools/list'
})
assert response.status_code == 200
2. Test with Custom Settings
def test_custom_settings(pyramid_app):
"""Configure custom settings for your test."""
settings = {
"mcp.server_name": "custom-test-server",
"mcp.mount_path": "/api/mcp"
}
app = pyramid_app(settings=settings)
# Test with custom configuration
response = app.post_json('/api/mcp', {...})
assert response.status_code == 200
3. Test with Specific Views
def test_with_views(pyramid_app):
"""Add specific views for testing."""
def my_test_view(request):
return {"message": "test"}
views = [
(my_test_view, "test_route", {"renderer": "json"})
]
app = pyramid_app(views=views)
# Test the added view
response = app.get('/test_route')
assert response.json == {"message": "test"}
4. Test with Limited Scanning
def test_scoped_tools(pyramid_app):
"""Limit tool scanning to specific module."""
app = pyramid_app(scan_path="tests.unit.specific_module")
# Only tools from specific_module will be available
response = app.post_json('/mcp', {
'jsonrpc': '2.0',
'id': 1,
'method': 'tools/list'
})
# Verify only expected tools are listed
5. Test with Ignore Patterns
def test_ignore_problematic_modules(pyramid_app):
"""Ignore specific modules during scanning."""
app = pyramid_app(ignore=["tests.cornice", "tests.integration.slow"])
# Tools from ignored modules won't be available
response = app.post_json('/mcp', {
'jsonrpc': '2.0',
'id': 1,
'method': 'tools/list'
})
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.
- 2d ago First seen · 165 lines · 1,211 tokens per session scan A 2db440197773
test-patterns is a cursor rule published in the GitHub repository cartaorobbin/pyramid-mcp (3 stars, last pushed 10mo ago), licensed MIT. It adds 1,211 tokens to every session, about $0.0061 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
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.