How do I install the Mk Vulnerability Scanner skill?

Run npx skillmds@latest add ngocsangyem/mk-vulnerability-scanner-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mk Vulnerability Scanner safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mk Vulnerability Scanner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mk Vulnerability Scanner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mk Vulnerability Scanner?

ngocsangyem (@ngocsangyem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mk Vulnerability Scanner by ngocsangyem

Name: Mk Vulnerability Scanner
Author: ngocsangyem

File contents

Vulnerability Scanner

Think like an attacker, defend like an expert.

When to Use

Security audit of a project or module
Before shipping code that handles auth, payments, or user data
When asked to "scan for vulnerabilities", "security check", "audit security"
When mk:cso delegates specific scanning tasks

Core Principles

Principle	Application
Assume Breach	Design as if attacker already inside
Zero Trust	Never trust, always verify
Defense in Depth	Multiple layers, no single point
Least Privilege	Minimum required access only
Fail Secure	On error, deny access

Process

Map attack surface — entry points, data flows, trust boundaries, assets
Load scanning methodology — read references/scanning-methodology.md
Reconnaissance — understand technology stack, entry points, data flows
Discovery — configuration review, dependency analysis, code pattern search
Analysis — validate findings, eliminate false positives, score risks
Report — each finding: What, Where, Why, Impact, How to fix

Threat Modeling Questions

Before scanning, ask: What are we protecting? Who would attack? How? What's the impact?

References

Reference	When to load	Content
scanning-methodology.md	Step 2 — executing scan	OWASP Top 10, supply chain, code patterns, risk prioritization, reporting format

Runtime Scripts

Script	Purpose	Usage
`security-scan.py`	Security pattern scanning	`.cursor/skills/.venv/bin/python3 <path-to-security-scan.py>`
`injection-audit.py`	Prompt injection detection	`.cursor/skills/.venv/bin/python3 <path-to-injection-audit.py>`

Gotchas

False positives in test fixtures: Security scan flags intentionally insecure test data → Exclude test/fixtures/ and mocks/ from vulnerability scans
Dependency confusion attacks missed: Scanner checks known CVEs but not package name typosquatting → Cross-reference package names against known typosquat databases

---name: mk-vulnerability-scanner-3description: Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE/CSO infra audits (mk:cso).---# Vulnerability Scanner> Think like an attacker, defend like an expert.## When to Use- Security audit of a project or module- Before shipping code that handles auth, payments, or user data- When asked to "scan for vulnerabilities", "security check", "audit security"- When mk:cso delegates specific scanning tasks## Core Principles| Principle | Application || -------------------- | ------------------------------------ || **Assume Breach** | Design as if attacker already inside || **Zero Trust** | Never trust, always verify || **Defense in Depth** | Multiple layers, no single point || **Least Privilege** | Minimum required access only || **Fail Secure** | On error, deny access |## Process1. **Map attack surface** — entry points, data flows, trust boundaries, assets2. **Load scanning methodology** — read `references/scanning-methodology.md`3. **Reconnaissance** — understand technology stack, entry points, data flows4. **Discovery** — configuration review, dependency analysis, code pattern search5. **Analysis** — validate findings, eliminate false positives, score risks6. **Report** — each finding: What, Where, Why, Impact, How to fix## Threat Modeling QuestionsBefore scanning, ask: What are we protecting? Who would attack? How? What's the impact?## References| Reference | When to load | Content || ------------------------------------------------------------------- | ----------------------- | -------------------------------------------------------------------------------- || **[scanning-methodology.md](./references/scanning-methodology.md)** | Step 2 — executing scan | OWASP Top 10, supply chain, code patterns, risk prioritization, reporting format |## Runtime Scripts| Script | Purpose | Usage || -------------------- | -------------------------- | --------------------------------------------------------------------- || `security-scan.py` | Security pattern scanning | `.cursor/skills/.venv/bin/python3 <path-to-security-scan.py>` || `injection-audit.py` | Prompt injection detection | `.cursor/skills/.venv/bin/python3 <path-to-injection-audit.py>` |## Gotchas- **False positives in test fixtures**: Security scan flags intentionally insecure test data → Exclude test/fixtures/ and **mocks**/ from vulnerability scans- **Dependency confusion attacks missed**: Scanner checks known CVEs but not package name typosquatting → Cross-reference package names against known typosquat databases

Frequently asked questions

Mk Vulnerability Scanner