security-scan

Detect secrets, dependency vulnerabilities, and misconfigurations in codebases.

53|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/cosmix/claude-code-setup --skill security-scan-cosmix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/cosmix/claude-code-setup/tree/main/skills/security-scan
Command: npx skills add https://github.com/cosmix/claude-code-setup --skill security-scan-cosmix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides quick, routine security checks that should be run frequently during development. These are lightweight scans designed to catch common issues early, not comprehensive audits.

Core Features & Use Cases

  • Secret Detection: Scan for hardcoded keys and credentials.
  • Dependency & Configuration Checks: Quick vulnerability and misconfiguration checks.
  • Pre-commit / PR Hygiene: Lightweight security checks before merges.

Quick Start

Run a fast security sweep on the repository to catch obvious secrets and outdated dependencies.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I detect hardcoded secrets in my codebase before committing?

Secret detection scans your repository for hardcoded keys, credentials, and tokens using tools like trufflehog and gitleaks. Run these checks as pre-commit hooks to catch exposed secrets before they reach version control, preventing accidental credential leaks in your repository history.

Can I run security scans automatically in pull requests?

Yes, security scans integrate into CI/CD pipelines and pull request reviews to automatically check for secrets, dependency vulnerabilities, and misconfigurations before merges. This enables routine hygiene checks at each code change without manual intervention.

What kinds of vulnerabilities does a quick security scan catch?

Quick security scans detect hardcoded secrets, outdated or vulnerable dependencies, and common misconfigurations using lightweight tools like semgrep and grep. These routine checks catch obvious issues early during development without requiring comprehensive audits.

Do I need special tooling to run security checks on multiple programming languages?

No, multi-language scans use common, language-agnostic tools like grep, trufflehog, gitleaks, and semgrep with configurable rules. This approach supports codebases mixing different languages with a single lightweight scanning workflow.

How often should I run routine security checks during development?

Routine security checks run frequently—at pre-commit hooks, during pull request reviews, and in CI checks—to catch issues early. These lightweight scans are designed for continuous use throughout development without slowing your workflow.