mcpnuke: Skill for Cursor

Add mcpnuke Patterns

Pattern Files

File	Purpose	Used By
mcpnuke/patterns/rules.py	Static regex for metadata analysis	Static checks (injection, permissions, theft, etc.)
mcpnuke/patterns/probes.py	Probe payloads and response analysis	Behavioral checks (tool_probes, resource_poisoning)

Adding Static Patterns

1. Define the pattern list in rules.py

YOUR_PATTERNS = [
    r"pattern_one",
    r"pattern_two",
]

Pattern guidelines:

• Use raw strings (r"...")
• Case-insensitive matching is done by the caller (re.IGNORECASE)
• Use \s+ for whitespace, \b for word boundaries
• Use .{0,30} for bounded wildcards (not .*)
• Test each pattern against both positive and negative examples

2. Add tests in tests/test_patterns.py

def test_your_patterns_match():
    text = "String that should match"
    matches = [p for p in YOUR_PATTERNS if re.search(p, text, re.IGNORECASE)]
    assert len(matches) >= 1


def test_your_patterns_no_false_positive():
    text = "Normal safe string"
    matches = [p for p in YOUR_PATTERNS if re.search(p, text, re.IGNORECASE)]
    assert len(matches) == 0

3. Run tests (TDD: write tests FIRST, then patterns)

Follow superpowers test-driven-development: write the test assertions before adding patterns to rules.py. Watch them fail (RED), then add patterns (GREEN).

uv run pytest tests/test_patterns.py -v

Adding Probe Payloads

In probes.py

Injection probes (sent to tools):

YOUR_PROBES = [
    f"payload_with_{CANARY}",
    "payload_two",
]

Response analysis patterns (checked in tool output):

YOUR_RESPONSE_PATTERNS = [
    r"pattern_to_find_in_responses",
]

Rules:

• Probes should be safe — they test for vuln without causing damage
• Use the CANARY string (MCP_PROBE_8f4c2a) to detect reflection
• Response patterns use the same regex conventions as rules.py

Existing Pattern Sets (reference)