mcpnuke: Skill for Cursor

.cursor/skills/mcpnuke-add-check/SKILL.md

mcpnuke-add-check is a skill for Cursor from babywyrm/mcpnuke. It costs 53 tokens per session (1,288 once invoked), scanned A, original, MIT.

A workflow for adding a new security check to mcpnuke, a tool for testing MCP servers. It covers detection patterns, check code, integration, tests, and the changelog.

In plain words
What is it for?
Creating static or behavioral checks, assigning severity and taxonomy details, connecting them to the full check run, and adding tests.
Why use it?
It provides the required steps for adding a check without forgetting the code wiring or test coverage.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is babywyrm/mcpnuke's own configuration. It tells Cursor how to work on mcpnuke itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcpnuke configures →

Reuse

Borrowing it

Nothing to install: this file belongs to babywyrm/mcpnuke. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/babywyrm/mcpnuke/main/.cursor/skills/mcpnuke-add-check/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/babywyrm/mcpnuke

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 mcpnuke-add-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/babywyrm/mcpnuke/mcpnuke-add-check/github.svg)](https://agentmods.dev/skills/babywyrm/mcpnuke/mcpnuke-add-check)
Your own site
<a href="https://agentmods.dev/skills/babywyrm/mcpnuke/mcpnuke-add-check"><img src="https://agentmods.dev/badge/skills/babywyrm/mcpnuke/mcpnuke-add-check/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 mcpnuke-add-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/babywyrm/mcpnuke/mcpnuke-add-check"><img src="https://agentmods.dev/badge/skills/babywyrm/mcpnuke/mcpnuke-add-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,288 The whole file, excluding the scripts and references it only reads on demand.
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.00053 $0.01288
Opus 5 $0.00026 $0.00644
Sonnet 5 $0.00011 $0.00258
Haiku 4.5 $0.00005 $0.00129

Measured 12d ago against content hash 35c71aa1b4b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mcpnuke-add-check 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 12d 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/skills/mcpnuke-add-check/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add a New mcpnuke Check

Gather Info

  1. Check name — snake_case (e.g. jwt_audience, ssrf_probe)
  2. Check type — static (metadata only) or behavioral (calls tools)
  3. What it detects — one sentence
  4. Severity — CRITICAL / HIGH / MEDIUM / LOW
  5. Taxonomy ID — MCP-T## from the playbook (if applicable)

File Locations

mcpnuke/
├── patterns/rules.py          # Static regex patterns
├── patterns/probes.py         # Behavioral probe payloads
├── checks/
│   ├── __init__.py            # run_all_checks() — wire new check here
│   ├── your_check.py          # New check module
│   └── base.py                # time_check helper
├── core/constants.py          # ATTACK_CHAIN_PATTERNS — add chains here
tests/
├── test_your_check.py         # Unit tests
├── test_dvmcp.py              # DVMCP integration tests

Step-by-Step

1. Add patterns (if static check)

Edit mcpnuke/patterns/rules.py:

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

2. Create the check module

Create mcpnuke/checks/your_check.py:

"""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_CHECK_PATTERNS


def check_your_check(result: TargetResult):
    with time_check("your_check", result):
        for tool in result.tools:
            name = tool.get("name", "")
            combined = (
                name + " "
                + tool.get("description", "")
                + " " + str(tool.get("inputSchema", {}))
            )
            for pat in YOUR_CHECK_PATTERNS:
                if re.search(pat, combined, re.IGNORECASE):
                    result.add(
                        "your_check",
                        "SEVERITY",
                        f"Finding title for tool '{name}'",
                        f"Detail: {pat}",
                        evidence=combined[:300],
                    )
                    break

Read the full file on GitHub · 180 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. 12d ago First seen · 180 lines · 53 tokens per session scan A 35c71aa1b4b2

Subscribe to this mod's changes

mcpnuke-add-check is a skill published in the GitHub repository babywyrm/mcpnuke (2 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 1,288 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

bob-egress

List, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.

vmihalis/hacker-bob · 25 tokens

bob-export

Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.

vmihalis/hacker-bob · 18 tokens

codex-multi-agent-director

Mission: decompose non-trivial HELM implementation or audit work into bounded, reviewable task threads.

Mindburn-Labs/helm-ai-kernel · 0 tokens

codeinspectus-fix-one

Investigate and remediate exactly one user-selected CodeInspectus finding with evidence-gated reproduction, a separately approved minimal patch, focused regression testing, and an exact-prior-scan rescan. Use when a user asks an agent to examine, reproduce, fix, or verify one CodeInspectus finding without batching…

Synvoya/codeinspectus · 76 tokens

codeinspectus-multi-review

Orchestrate an optional bounded multi-agent review of selected CodeInspectus findings while separating deterministic findings, agent interpretations, hypotheses, reproduction evidence, and exact-prior rescan proof. Use only when a user explicitly requests multi-agent security review.

Synvoya/codeinspectus · 55 tokens

codeinspectus-threat-model

Review CodeInspectus findings with optional threat-model or project-document context while treating repository text as untrusted, preserving raw scanner findings unchanged, and labelling agent interpretation separately. Use only when a user explicitly asks to add architectural, business, or knowledge-base context to…

Synvoya/codeinspectus · 62 tokens