security-testing

Identify and validate security vulnerabilities in software applications.

6|3|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/pacphi/ampel --skill security-testing-pacphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-testing
Source: https://github.com/pacphi/ampel/tree/main/.claude/skills/security-testing
Command: npx skills add https://github.com/pacphi/ampel --skill security-testing-pacphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured security testing and auditing across your app, validating authentication, authorization, input validation, and dependency security.

Core Features & Use Cases

  • OWASP Top 10 Coverage: Systematic checks across common vulnerabilities
  • Auth & AuthZ Validation: Endpoints, tokens, permissions
  • Dependency Scanning: Vulnerabilities in dependencies
  • Config & Secrets Review: No leaked secrets in code or logs

Quick Start

claude-flow run security-test-suite on the app; set up CI to run OWASP tests on every PR

Frequently Asked Questions about security-testing

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

FAQPage Schema
How do I identify OWASP Top 10 vulnerabilities in my application?

OWASP Top 10 identification validates security weaknesses across authentication, authorization, input validation, dependencies, and misconfigurations. This Skill performs automated checks aligned to OWASP 2021 standards, scanning your codebase and producing reproducible audit outputs suitable for security reviews and compliance.

Can I run security testing automatically in my CI/CD pipeline?

Yes. This Skill integrates with CI/CD workflows to run OWASP security tests on every pull request and commit. It executes SAST and DAST scanning, dependency checks, and secrets scanning, producing structured audit reports without manual intervention.

What does SAST and DAST security scanning cover?

SAST (Static Application Security Testing) analyzes source code for vulnerabilities; DAST (Dynamic Application Security Testing) tests running applications for runtime exploits. This Skill supports both approaches alongside dependency vulnerability scanning and secrets detection across authentication, authorization, and data exposure scenarios.

How do I validate that secrets and credentials aren't exposed in my codebase?

Secrets scanning within this Skill detects leaked credentials, API keys, and tokens in source code and logs. It audits configuration files and dependencies to ensure no sensitive data is exposed, integrating into CI/CD for continuous validation.

Does this work for dependency vulnerability scanning?

Yes. Dependency scanning identifies known security vulnerabilities in third-party libraries and packages your application relies on. Results integrate into audit reports and CI/CD workflows for automated remediation tracking.

What's the difference between security audits and vulnerability scanning?

Security audits perform comprehensive, structured reviews across multiple vulnerability categories using systematic OWASP checks; vulnerability scanning targets specific weaknesses in dependencies and code. This Skill combines both approaches, executing full audits or focused scans depending on your workflow stage.