security

Detect OWASP Top 10, secrets, and dependency vulnerabilities in codebases.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/Wondermove-Inc/calab-claude-plugin --skill security-wondermove-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/Wondermove-Inc/calab-claude-plugin/tree/main/plugins/calab-plugin/skills/security
Command: npx skills add https://github.com/Wondermove-Inc/calab-claude-plugin --skill security-wondermove-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security scanning is often manual, time-consuming, and prone to missing critical vulnerabilities in code, secrets, and dependencies, which can lead to insecure deployments.

Core Features & Use Cases

  • OWASP Top 10 checks to detect common web security risks in applications.
  • Secrets detection to uncover hard-coded API keys, tokens, and credentials.
  • Dependency vulnerability analysis to identify vulnerable libraries and components.
  • Integration use case: run security scans during CI/CD on pull requests and generate actionable reports for developers.

Quick Start

Use the security Skill to run a full scan: /security [path] Narrow the scope with: /security --owasp [path] or /security --secrets [path] Check dependencies only: /security --deps Run all checks: /security --full Output reports are written to .claude/docs/active/{feature}/security-review.md

Frequently Asked Questions about security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OWASP Top 10 checks and secret detection across my codebase?

Automate security vulnerability detection by running a full scan with the security Skill, which performs OWASP Top 10 checks, secret detection, and dependency analysis to output a Markdown security report.

What is the best way to scan dependencies for vulnerable libraries before a deployment?

Scanning dependencies for vulnerable libraries is done by running a targeted dependency vulnerability analysis, which identifies insecure components and outputs the results to a Markdown security report.

How do I detect hard-coded API keys and tokens in my source code?

Detect hard-coded API keys and tokens by running a dedicated secrets detection scan on your codebase path, which uncovers exposed credentials and documents them in a security review report.

Can I narrow an automated security review to only specific vulnerability checks?

Yes, you can narrow the security review scope by specifying flags for OWASP checks or secrets detection only, allowing you to target specific vulnerability categories instead of running a full scan.

Where does the automated security vulnerability review report get saved?

The automated security vulnerability review report gets saved as a Markdown file at .claude/docs/active/{feature}/security-review.md, providing developers with actionable findings.