security

Scan code repositories for security vulnerabilities and generate remediation reports.

Updated Feb 25, 2026

Search Tags:#code quality #security #vulnerability #owasp #secrets #scan #remediate

Ready to run

npx skills add https://github.com/LayerDynamics/Lore --skill security-layerdynamics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/security
Command: npx skills add https://github.com/LayerDynamics/Lore --skill security-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill proactively identifies and helps remediate security vulnerabilities within your codebase, protecting your project from common threats like exposed secrets, injection attacks, and insecure configurations.

Core Features & Use Cases

Comprehensive Scanning: Detects hardcoded secrets, OWASP vulnerability patterns (SQLi, XSS, Command Injection), and insecure configurations.
Automated Remediation: Guides the user through fixing identified vulnerabilities, prioritizing critical issues.
Use Case: Run a security scan on your project to find any accidentally committed API keys or potential SQL injection flaws before deploying to production.

Quick Start

Run a security scan on the current project directory.

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 repository for hardcoded secrets and security vulnerabilities?▼

To scan for security vulnerabilities and hardcoded secrets, run a security scan on your project directory. It uses grep pattern matching across file types to detect exposed secrets, OWASP patterns like SQLi, and insecure configurations, generating a detailed vulnerability report.

What is the process for automated remediation of OWASP vulnerabilities found in a project?▼

Automated remediation for OWASP vulnerabilities guides you through fixing identified issues by severity. After scanning detects injection attacks or insecure configurations, it prioritizes critical findings and provides step-by-step instructions to remediate high, medium, and low severity vulnerabilities.

Can I detect insecure configurations and exposed API keys before deploying to production?▼

Yes, you can detect insecure configurations and exposed API keys before production by running a security scan. It proactively identifies accidentally committed secrets and common threats like injection attacks, providing a detailed report to fix issues prior to deployment.

Does this security scanner work without external dependencies or language-specific linters?▼

Yes, the security scanner works without external dependencies. It relies on grep for pattern matching across various file types to identify hardcoded secrets and OWASP vulnerability patterns, requiring no additional language-specific linters or complex environment setup.

How are vulnerability findings prioritized when scanning a codebase?▼

Vulnerability findings are prioritized by severity level. The scan evaluates the codebase for security issues and categorizes them into critical, high, medium, and low severity findings, guiding you through fixing the most critical vulnerabilities first during automated remediation.