security-audit

Scan code repositories for vulnerabilities and leaked secrets using static analysis tools.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/TECHKNOWMAD-LABS/cortex-research-suite --skill security-audit-techknowmad-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/TECHKNOWMAD-LABS/cortex-research-suite/tree/main/skills/security-audit
Command: npx skills add https://github.com/TECHKNOWMAD-LABS/cortex-research-suite --skill security-audit-techknowmad-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bandit, semgrep, and includes scripts (resource) and rules (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying security vulnerabilities and leaked secrets within code repositories, ensuring code is safe before deployment.

Core Features & Use Cases

  • Automated Scanning: Utilizes tools like Bandit and Semgrep for static analysis.
  • Secret Detection: Identifies hardcoded API keys, tokens, and other sensitive credentials.
  • Use Case: Before deploying a new feature, run this Skill to automatically scan the codebase for common vulnerabilities such as SQL injection, cross-site scripting, and exposed API keys, generating a clear report of findings.

Quick Start

Run a security audit on the current directory to check for vulnerabilities and secrets.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I scan my code repository for vulnerabilities and exposed secrets?

To scan code for vulnerabilities and exposed credentials, you can run automated static analysis and secret detection tasks on your repository directory to generate a report of findings.

What's the best way to detect hardcoded API keys and tokens before deployment?

The best way to detect hardcoded API keys is to run pre-deployment security audits using static analysis tools and custom regex patterns designed for credential exposure checks.

How does static analysis find vulnerabilities like SQL injection in my codebase?

Static analysis finds vulnerabilities like SQL injection by scanning source code patterns without executing the program, relying on predefined rules to identify insecure code structures.

Does this security audit use Bandit and Semgrep for code scanning?

Yes, the security audit integrates directly with Bandit and Semgrep to perform comprehensive static analysis and identify common code-level vulnerabilities.

Can I check for cross-site scripting and other common security flaws automatically?

Yes, you can automatically check for cross-site scripting and similar flaws by running an automated security audit configured with static application security testing rules.

When do I need to run a security audit on my codebase?

You need to run a security audit before deploying new features to ensure code safety, verify there are no leaked secrets, and assess vulnerabilities early in the development lifecycle.