agentsclimarketplace

Mk vulnerability scanner

Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-vulnerability-scanner

Production ready. AI Agent Workflow System for Claude Code

Install
npx -y skills add ngocsangyem/MeowKit --skill mk-vulnerability-scanner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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).

SKILL.md

3.1 KB, as published. Nobody here has run it

<!-- Split for progressive disclosure (checklist #11, #14): 278 → ~55 lines -->

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

PrincipleApplication
Assume BreachDesign as if attacker already inside
Zero TrustNever trust, always verify
Defense in DepthMultiple layers, no single point
Least PrivilegeMinimum required access only
Fail SecureOn error, deny access

Process

  1. Map attack surface — entry points, data flows, trust boundaries, assets
  2. Load scanning methodology — read references/scanning-methodology.md
  3. Reconnaissance — understand technology stack, entry points, data flows
  4. Discovery — configuration review, dependency analysis, code pattern search
  5. Analysis — validate findings, eliminate false positives, score risks
  6. 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

ReferenceWhen to loadContent
scanning-methodology.mdStep 2 — executing scanOWASP Top 10, supply chain, code patterns, risk prioritization, reporting format

Runtime Scripts

ScriptPurposeUsage
security-scan.pySecurity pattern scanning.agents/skills/.venv/bin/python3 .codex/scripts/security-scan.py
injection-audit.pyPrompt injection detection.agents/skills/.venv/bin/python3 .codex/scripts/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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.