security_audit

Audit codebases for OWASP Top 10, CVEs, secrets, and security headers.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill security-audit-hjemmesidekongen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security_audit
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/smedjen/skills/security-audit
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill security-audit-hjemmesidekongen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust security in software development by automating the detection of common vulnerabilities and misconfigurations before they reach production.

Core Features & Use Cases

  • OWASP Top 10 Assessment: Comprehensive review against the latest OWASP Top 10 vulnerabilities.
  • Dependency Scanning: Identifies known vulnerabilities (CVEs) in project dependencies.
  • Secret Detection: Scans code and commit history for hardcoded secrets and credentials.
  • Header Review: Assesses Content Security Policy (CSP) and other security headers.
  • Use Case: Before merging a pull request that modifies authentication logic, run this security audit to ensure no new vulnerabilities are introduced and all security best practices are followed.

Quick Start

Run a full security audit on the current project, checking for OWASP vulnerabilities, secrets, and dependency issues.

Frequently Asked Questions about security_audit

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

FAQPage Schema
How do I run a security audit to check my codebase for OWASP Top 10 vulnerabilities?

A security audit checks your codebase against the OWASP Top 10 to identify common vulnerabilities and misconfigurations. This skill automates that comprehensive review process to help harden your code before release.

What is the best way to scan dependencies for known CVEs before merging a pull request?

Scanning dependencies for known CVEs before merging a pull request is best handled by automated dependency scanning. This skill identifies known vulnerabilities in your project dependencies to ensure no new risks are introduced.

Can I detect hardcoded secrets and credentials in my commit history?

Yes, you can detect hardcoded secrets and credentials in your commit history. This skill includes secret detection capabilities that scan both your current code and commit history for exposed sensitive information.

How do I review Content Security Policy and other security headers in my project?

To review Content Security Policy and other security headers, you need a dedicated header assessment. This skill evaluates your CSP and related headers to ensure proper security configurations are applied.

Does this security audit work for hardening code before a release?

Yes, this security audit works for hardening code before a release. It is specifically designed to automate the detection of vulnerabilities, dependency issues, and secrets as a pre-release validation step.