security

Audit code for security vulnerabilities, hardcoded secrets, and dependency risks.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ps-carvalho/spavn-agents --skill security-ps-carvalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/ps-carvalho/spavn-agents/tree/main/.opencode/skills/security
Command: npx skills add https://github.com/ps-carvalho/spavn-agents --skill security-ps-carvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies security vulnerabilities and hardcoded secrets within your codebase, ensuring a more secure development process.

Core Features & Use Cases

  • Vulnerability Auditing: Scans code against OWASP Top 10 and common attack vectors.
  • Secret Detection: Flags hardcoded API keys, passwords, and tokens.
  • Dependency Scanning: Checks for known vulnerabilities in project dependencies.
  • Use Case: Before merging a new feature, run this Skill to automatically audit the code for critical security flaws and prevent accidental exposure of sensitive credentials.

Quick Start

Use the security skill to audit the attached files for vulnerabilities and secrets.

Frequently Asked Questions about security

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

FAQPage Schema
How do I scan my code for security vulnerabilities and hardcoded secrets?

To audit code for vulnerabilities and secrets, run this Skill in a secure environment with access to your project files. It automatically scans against the OWASP Top 10, flags hardcoded API keys or tokens, and checks dependencies for known risks.

What is the best way to check project dependencies for known vulnerabilities?

The best way to check project dependencies for known vulnerabilities is to run an automated dependency scanning audit. This Skill evaluates your project files to identify risky dependencies and hardcoded credentials before merging new features.

Can I detect hardcoded API keys and passwords in my codebase before merging?

You can detect hardcoded API keys and passwords in your codebase by running a secret detection audit. This Skill scans project files to flag exposed tokens and credentials, preventing accidental exposure of sensitive information during development.

Does this vulnerability audit cover OWASP Top 10 risks and input validation?

Yes, this vulnerability audit covers OWASP Top 10 risks, input validation, authentication, and modern attack vectors. It scans your codebase thoroughly to identify these critical security flaws and ensure a secure development process.

Do I need a specific environment setup to run a security audit on my project files?

You need a secure environment with direct access to your project files to run this security audit. This setup allows the scanner to accurately evaluate code for vulnerabilities, secrets, and dependency risks without external limitations.

When should I run a code vulnerability audit during the software development lifecycle?

You should run a code vulnerability audit before merging a new feature into your codebase. Performing this scan ensures that security vulnerabilities, hardcoded secrets, and dependency risks are detected and resolved early in development.