codebase-quality:security

Scan codebases for secrets, dependency vulnerabilities, and injection risks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bjornslib/cobuilder-harness --skill codebase-quality-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-quality:security
Source: https://github.com/bjornslib/cobuilder-harness/tree/main/.claude/skills/codebase-quality/security
Command: npx skills add https://github.com/bjornslib/cobuilder-harness --skill codebase-quality-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and prevent security vulnerabilities including exposed secrets, dependency vulnerabilities, and code injection risks.

Core Features & Use Cases

  • Secrets detection across codebases to prevent leakage of API keys, tokens, and credentials.
  • Dependency vulnerability auditing for both frontend and backend packages, with guidance to update or patch vulnerable libraries.
  • Injection risk checks and secure coding patterns, including parameterized queries and input sanitization.
  • Use Case: Integrate security scans into pull requests to ensure only secure code proceeds to review.

Quick Start

Run the security scan at the start of an audit to identify secrets, dependencies, and injection risks.

Frequently Asked Questions about codebase-quality:security

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

FAQPage Schema
How do I scan my codebase for exposed secrets and API keys?▼

To scan your codebase for exposed secrets and API keys, run a security scan that detects credentials across files to prevent leakage. It identifies tokens and keys early, providing actionable remediation guidance to secure sensitive data.

What is the best way to check for dependency vulnerabilities before merging code?▼

The best way to check for dependency vulnerabilities before merging code is integrating security scans into pull requests. This audits frontend and backend packages, ensuring only secure code proceeds to review with clear patch guidance.

How do I detect injection risks and verify secure coding patterns?▼

To detect injection risks and verify secure coding patterns, use static analysis to scan for parameterized queries and input sanitization. The scan highlights injection vulnerabilities and provides actionable remediation steps to secure code.

Can I integrate security scans into CI pipelines and pre-commit checks?▼

Yes, you can integrate security scans into CI pipelines, pre-commit, and pre-merge checks. Applying scans at these stages detects secrets, dependency vulnerabilities, and injection risks early in the development lifecycle.

When do I need to run a codebase security audit?▼

You need to run a codebase security audit at the start of a review cycle to identify secrets, dependencies, and injection risks. Running scans during pull requests catches vulnerabilities early before code proceeds to production.