ck:security-scan

Detect security vulnerabilities, hardcoded secrets, and dependency issues in codebases.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-security-scan-auxi-wardrobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:security-scan
Source: https://github.com/auxi-wardrobe/auxi-all-in/tree/main/.agents/skills/security-scan
Command: npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-security-scan-auxi-wardrobe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps automate the process of scanning codebases for security vulnerabilities, hardcoded secrets, dependency issues, and OWASP patterns, ensuring codebases are secure before releases.

Core Features & Use Cases

  • Security Vulnerability Scanning: Identifies common security issues like SQL injection, XSS, and command injection.
  • Secret Detection: Scans for hardcoded credentials and sensitive information in the codebase.
  • Dependency Audit: Checks for outdated or vulnerable dependencies in the project.
  • Use Case: Before deploying code to production, use this skill to scan the repository for any potential security risks.

Quick Start

Run a full security scan on your project with the command: /ck:security-scan

Frequently Asked Questions about ck:security-scan

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

FAQPage Schema
How do I automate security vulnerability scanning for my codebase before deployment?

Automate security vulnerability scanning by running a full audit to identify SQL injection, XSS, and command injection risks in your codebase before production deployment. It uses regex patterns and reasoning to detect OWASP issues.

How do I detect hardcoded secrets and credentials in my source code?

Detect hardcoded secrets and credentials by scanning the codebase for sensitive information using regex pattern matching. It identifies exposed keys and passwords to ensure codebases remain secure before releases.

What is the best way to check for vulnerable dependencies during a code review?

The best way to check for vulnerable dependencies during a code review is to run an automated dependency audit. This scans the project for outdated or risky packages to ensure no known issues exist.

Does automated secret detection work without external resources?

Automated secret detection requires access to external resources for accurate pattern matching and vulnerability assessment. These external references are necessary to validate hardcoded credentials and security risks.

Can I scan for OWASP patterns automatically across an entire software project?

You can scan for OWASP patterns automatically across an entire software project by initiating a full security scan. It applies regex patterns and reasoning to detect common security vulnerabilities and dependency issues.

Why should I run a dependency audit and vulnerability scan before a release?

Run a dependency audit and vulnerability scan before a release to identify hardcoded secrets, outdated packages, and security vulnerabilities. This ensures the production codebase is secure and compliant with standards.