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-development)<a href="https://agentmods.dev/rules/babywyrm/mcpnuke/mcpnuke-development"><img src="https://agentmods.dev/badge/rules/babywyrm/mcpnuke/mcpnuke-development/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.
<a href="https://agentmods.dev/rules/babywyrm/mcpnuke/mcpnuke-development"><img src="https://agentmods.dev/badge/rules/babywyrm/mcpnuke/mcpnuke-development.svg" alt="Reviewed on agentmods" width="80" 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.01093 | $0.01093 |
| Opus 5.5 | $0.00437 | $0.00437 |
| Sonnet 5.5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
mcpnuke-development 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcpnuke Development Standards
Project Identity
mcpnuke is an MCP red teaming and security scanner. Version 6.21.1. Python 3.11+.
Package manager: uv. Test runner: uv run pytest tests/ -v.
Superpowers Workflow (mandatory)
All development on mcpnuke follows the superpowers skills framework:
- brainstorming before any new feature, check, or transport
- writing-plans before multi-step implementation work
- test-driven-development for all check modules and pattern changes — RED-GREEN-REFACTOR, no exceptions
- systematic-debugging for any test failure or scan anomaly — form hypothesis before changing code
- verification-before-completion before claiming anything is done — run
uv run pytest tests/ -vand confirm output - requesting-code-review after completing a feature branch
Code Conventions
- Strong typing throughout: use
dict,list,frozenset,int,strtype hints on all functions - Module-level constants:
UPPER_SNAKE_CASE, typed explicitly (e.g._NAME_MULTIPLIER: int = 3) - Check functions signature:
check_name(result: TargetResult)for static,check_name(session: MCPSessionProtocol, result: TargetResult, probe_opts: dict | None = None)for behavioral - Credential regexes belong in
patterns/credentials.pyonly, in the tier that matches their false-positive risk — never inrules.py,probes.py, or a check module - Every check wrapped in
with time_check("check_name", result): - Findings via
result.add(check_name, severity, title, detail, evidence=...) - Severity levels: CRITICAL, HIGH, MEDIUM, LOW
Testing Requirements
- Every new check needs a dedicated
tests/test_<check_name>.py - Minimum 3 tests per check: positive detection, clean/negative, timing recorded
- Use
conftest.pyfixtures:result_with_tools([{...}]) - Full suite must pass before any commit: 0 failed. Do not cite a hardcoded pass count.
- Also green before committing:
ruff check .at zero,mypy mcpnuke/at or below the CI ceiling.mcpnuke.core.*additionally enforcesdisallow_untyped_defs - DVMCP live tests gated behind
DVMCP_LIVE=1
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.
- 9d ago Changed fd4627c69859
- 21d ago Changed a037f9d717dd
- 23d ago Changed · +2 lines · +34 tokens per session 391f2a0e0d6a
- 1mo ago First seen · 83 lines · 1,059 tokens per session scan A 64b5715ac782
mcpnuke-development is a cursor rule published in the GitHub repository babywyrm/mcpnuke (2 stars, last pushed yesterday), licensed MIT. It adds 1,093 tokens to every session, about $0.0044 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.
Other cursor rules, from other repositories
architecture
This document outlines the fundamental architectural principles and patterns for the mcp-debug codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
testing
Testing contract — how to build and run tests in this repo.
python-code-validator
Validate generated Python at every step, not once at the end.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.
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.