vuln-research

vuln-research is a cursor rule for Cursor from briiirussell/cybersecurity-skills. It costs 117 tokens per session (2,490 once invoked), scanned A, original, MIT.

A detailed investigation of a CVE, which is a publicly recorded software security vulnerability. It examines affected versions, whether your code reaches the vulnerable part, available proof-of-concept attacks, patches, active exploitation, and temporary protections.

In plain words
What is it for?
Use it to investigate a specific CVE, verify whether your application is reachable, check for public exploits and fixes, and choose mitigation when immediate patching is not possible.
Why use it?
Knowing that a package has a vulnerability does not show whether your application can actually be affected. This assessment connects the public report to your code, deployment, patch options, and exposure window.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to investigate a specific CVE, verify whether your application is reachable, check for public exploits and fixes, and choose mitigation when immediate patching is not possible.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/briiirussell/cybersecurity-skills/vuln-research
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/briiirussell/cybersecurity-skills

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 vuln-research

README.md
[![agentmods](https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/vuln-research/github.svg)](https://agentmods.dev/rules/briiirussell/cybersecurity-skills/vuln-research)
Your own site
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/vuln-research"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/vuln-research/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 vuln-research

Your own site · 80×15
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/vuln-research"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/vuln-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 117 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,490 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.00117 $0.02490
Opus 5.5 $0.00047 $0.00996
Sonnet 5.5 $0.00023 $0.00498
Haiku 4.5 $0.00012 $0.00249

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

Security

Grade A, and why

vuln-research 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 today.

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.

adapters/cursor/vuln-research.mdc · 200 lines

How it starts

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

Vuln Research — CVE Deep-Dive and Applicability Assessment

When a CVE drops, the question isn't "do we have this package?" — dependency-audit answers that. The questions are:

  • Is the vulnerable code path actually invoked in our usage?
  • Is there a public proof-of-concept making this easy to exploit?
  • Is there a patch? When? What's our exposure window if we can't deploy in 24 hours?
  • If we can't patch, what's the mitigation?
  • Is CISA tracking it as actively exploited?

This skill walks that workflow end-to-end. Pairs with dependency-audit (which surfaces the CVE in the first place) and finding-triage (which closes the disposition loop).

Authorization

Research vulnerabilities in code, dependencies and systems the user owns or is authorized to assess. Reading advisories, patches and public write-ups is fine. Reproduce a vulnerability only in an isolated environment the user controls, never against a live system you aren't authorized to test. Pre-disclosure details stay with the people entitled to them (see Boundaries).

Workflow

Step 1 — Pull the canonical sources

Start with the authoritative descriptions; everything downstream is summarized or sometimes wrong.

  • NVD record — https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN
  • Vendor advisory — search the vendor's security page; this is usually the most accurate description of which versions are affected and what the fix is
  • GitHub Security Advisory — https://github.com/advisories/GHSA-... (often more concise than NVD, sometimes has detail NVD lacks; check the parent project's security tab)
  • CISA Known Exploited Vulnerabilities catalog — https://www.cisa.gov/known-exploited-vulnerabilities-catalog. If the CVE is here, treat as actively exploited — patch within CISA's stated due date
  • EPSS score — https://www.first.org/epss/ — Exploit Prediction Scoring System; a 30-day probability of exploitation. Useful tiebreaker between high-CVSS-low-EPSS vs medium-CVSS-high-EPSS

Read the full file on GitHub · 200 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. today Changed · +4 lines a1bd97dc5c27
  2. 1mo ago First seen · 196 lines · 117 tokens per session scan A 78a6307e5b64

Subscribe to this mod's changes

vuln-research is a cursor rule published in the GitHub repository briiirussell/cybersecurity-skills (435 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 2,490 once invoked, about $0.0005 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-30.