build-loop:security-scan

Scan repositories for common security vulnerabilities before pushing changes.

1|Updated Apr 6, 2026

Search Tags:#code quality #OWASP #vulnerability assessment #security scanning #repository security

Ready to run

npx skills add https://github.com/tyroneross/build-loop --skill build-loop-security-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-loop:security-scan
Source: https://github.com/tyroneross/build-loop/tree/main/skills/security-scan
Command: npx skills add https://github.com/tyroneross/build-loop --skill build-loop-security-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection of common security vulnerabilities in code repositories before pushing changes, ensuring code quality and security compliance.

Core Features & Use Cases

Security Vulnerability Scanning: Performs an automated scan for secrets, SQL injection, SSRF, rate limiting issues, missing security headers, and other common vulnerabilities.
Determine Findings Severity: Classifies findings into LOW, MEDIUM, and HIGH severity levels.
Pre-push Gate: Integrates as a pre-push gate to block pushes with HIGH severity findings, ensuring code is secure before merging.
Use Case: Before pushing code changes, run this Skill to automatically scan for potential security issues and address them promptly.

Quick Start

Run the security scan on the current repository with the command:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/security_scan.py" --path <repo>

Frequently Asked Questions about build-loop:security-scan

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

FAQPage Schema

How do I automate security scanning for vulnerabilities before pushing code?▼

Automated security scanning identifies common vulnerabilities like secrets, SQL injection, and SSRF before a push. This Skill runs a deterministic scan on your repository and blocks pushes containing HIGH severity findings from entering the main codebase.

What types of security vulnerabilities can an automated code repository scan detect?▼

An automated code repository scan detects secrets, SQL injection, SSRF, rate limiting issues, missing security headers, and other common vulnerabilities. Findings are classified into LOW, MEDIUM, and HIGH severity levels to help prioritize remediation efforts.

How does a pre-push security gate prevent vulnerable code from being merged?▼

A pre-push security gate blocks code pushes when HIGH severity findings are detected during the automated vulnerability assessment. This ensures that critical security issues are addressed promptly before any insecure code is merged into the main repository.

Can I run an OWASP security scan on my repository without installing external dependencies?▼

Yes, you can run this OWASP security scan without external dependencies. It uses a deterministic, model-independent scanner that requires no additional packages, executing directly via a Python script to assess repository code quality and security.

What is the best way to classify security findings by severity in a code repository?▼

Classifying security findings by severity involves categorizing detected vulnerabilities into LOW, MEDIUM, and HIGH levels. This automated scanner evaluates repository code and assigns severity ratings to help developers prioritize security fixes effectively.

How do I run a security scan on my current repository from the command line?▼

To run a security scan on your current repository, execute the Python scanner script with the repository path as an argument. This triggers an automated vulnerability assessment to identify security issues before you push changes.