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.
git clone --depth 1 https://github.com/babywyrm/mcpnukeWrote 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/babywyrm/mcpnuke/mcpnuke-checks)<a href="https://agentmods.dev/rules/babywyrm/mcpnuke/mcpnuke-checks"><img src="https://agentmods.dev/badge/rules/babywyrm/mcpnuke/mcpnuke-checks.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.00000 | $0.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
mcpnuke-checks 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Module Conventions
Static Check Template
"""One-line description of what this check detects."""
import re
from mcpnuke.core.models import TargetResult
from mcpnuke.checks.base import time_check
from mcpnuke.patterns.rules import YOUR_PATTERNS
def check_your_check(result: TargetResult) -> None:
with time_check("your_check", result):
for tool in result.tools:
name: str = tool.get("name", "")
desc: str = tool.get("description", "")
combined: str = f"{name} {desc} {tool.get('inputSchema', {})}"
for pat in YOUR_PATTERNS:
if re.search(pat, combined, re.IGNORECASE):
result.add("your_check", "SEVERITY", f"Title '{name}'", f"Detail: {pat}", evidence=combined[:300])
break
Behavioral Check Template
session is typed with MCPSessionProtocol from
mcpnuke.core.transports.base. Rely only on what it declares — call,
notify, close, wait_ready, protocol_mode. For anything HTTP-specific
(post_raw), gate on hasattr(session, "post_raw"), because stdio has no
header layer.
def check_your_check(
session: MCPSessionProtocol,
result: TargetResult,
probe_opts: dict | None = None,
) -> None:
opts: dict = probe_opts or {}
_log = opts.get("_log", lambda msg: None)
cache: dict = opts.get("_response_cache", {})
with time_check("your_check", result):
for tool in result.tools:
name: str = tool.get("name", "")
text: str | None = cache.get(name)
if text is None:
args = _build_safe_args(tool)
resp = _call_tool(session, name, args)
text = _response_text(resp)
if text:
# Analyze response
pass
Wiring Checklist
- Import in
checks/__init__.py - Call in correct phase (static / behavioral / deep probe)
- Add attack chains to
core/constants.pyif applicable - Add to README scan phases table
- Add to CHANGELOG
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.
- 8d ago First seen · 69 lines · 0 tokens per session scan A 3c31871e9507
mcpnuke-checks is a cursor rule published in the GitHub repository babywyrm/mcpnuke (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 544 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
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.