codepresso:security-audit

Scan codebases and developer machines for OWASP vulnerabilities and generate scored remediation reports.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill codepresso-security-audit-codepresso-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codepresso:security-audit
Source: https://github.com/codepresso-dev/codepresso-ai-plugin/tree/main/skills/security-audit
Command: npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill codepresso-security-audit-codepresso-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Security reviews are often skipped because they require deep expertise and manual effort across code, infrastructure, and developer machines. This Skill automates evidence gathering against the OWASP Top 10:2025 checklist and recent 2025-2026 incident patterns, then turns findings into a scored, prioritized remediation report. ## Core Features & Use Cases - Stack-agnostic scanning: Detects vulnerabilities in any repository (code, Docker, IaC, CI config) without needing the project's toolchain installed, plus an optional local credential-hygiene scan of the developer's machine. - Interview-driven verification: Narrows follow-up questions based on scan evidence so a human confirms what static scanning cannot judge, such as access-control logic and operational controls. - Scored remediation report: Produces a markdown report with a 0-100 posture score, letter grade, prioritized fixes, and real-incident rationale for each finding. - Use Case: Before a release, run the audit on your repo to catch hardcoded secrets, missing lockfiles, and misconfigured cloud resources, then file failing categories as Notion tasks for tracking. ## Quick Start Ask the AI to run a security audit on the current repository and generate a scored remediation report.

Frequently Asked Questions about codepresso:security-audit

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

FAQPage Schema
How do I run a security audit on my codebase?▼

Run the scan command against your repository path to gather evidence as JSON, answer the interview questions it triggers, then pipe the combined payload into the report command to get a scored markdown remediation report.

What does an OWASP Top 10 security scan check for?▼

It checks 12 categories covering injection, access control, supply chain risks, secrets, logging, and LLM prompt-injection or SSRF. Each item is grounded in the OWASP Top 10:2025 and recent incidents like the 2025 npm Shai-Hulud supply-chain attacks.

Does the security scanner work with Python or Go projects?▼

Yes, the scanner is stack-agnostic and reads files only, so it can audit Python, Go, or any repository from a Node-only environment. It never runs the project's build or tests, which means dynamic runtime issues are covered in the interview step instead.

Is it safe to scan my local machine for credentials?▼

The local scan only reports file paths, risk types, and environment variable names, and never prints secret values. It asks for permission before reading files like ~/.aws, ~/.ssh, or ~/.npmrc, and permission checks are POSIX-only.

Why does the scan report findings that are not real vulnerabilities?▼

The scanner surfaces candidates, not verdicts, so secrets in test fixtures or URLs in config files appear as findings by design. The interview step exists to confirm or dismiss each candidate before it appears in the final report.