test-patterns

test-patterns is a cursor rule for Cursor from cartaorobbin/pyramid-mcp. It costs 1,211 tokens per session, scanned A, original, MIT.

A standard pattern for creating Pyramid web applications in tests using the shared pyramid_app fixture.

In plain words
What is it for?
Use it to test requests, custom settings, routes, views, and other Pyramid application behavior.
Why use it?
It avoids each test inventing its own application setup, making tests more consistent and easier to maintain.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to test requests, custom settings, routes, views, and other Pyramid application behavior.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/cartaorobbin/pyramid-mcp/test-patterns
Install

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.

Clone the repo
git clone --depth 1 https://github.com/cartaorobbin/pyramid-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for test-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/test-patterns/github.svg)](https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/test-patterns)
Your own site
<a href="https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/test-patterns"><img src="https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/test-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/cartaorobbin/pyramid-mcp/test-patterns"><img src="https://agentmods.dev/badge/rules/cartaorobbin/pyramid-mcp/test-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,211 This file is loaded in full into every session.
When invoked 1,211 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01211 $0.01211
Opus 5.5 $0.00484 $0.00484
Sonnet 5.5 $0.00242 $0.00242
Haiku 4.5 $0.00121 $0.00121

Measured 2mo ago against content hash 2db440197773, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.cursor/rules/test-patterns.mdc · 165 lines

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'
    })

Read the full file on GitHub · 165 lines

Changes

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.

  1. 2mo ago First seen · 165 lines · 1,211 tokens per session scan A 2db440197773

Subscribe to this mod's changes

test-patterns is a cursor rule published in the GitHub repository cartaorobbin/pyramid-mcp (3 stars, last pushed 11d ago), licensed MIT. It adds 1,211 tokens to every session, about $0.0048 per session on Opus 5.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.