ln-621-security-auditor

Audit codebases for critical security vulnerabilities and generate structured findings.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-621-security-auditor-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-621-security-auditor
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-621-security-auditor
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-621-security-auditor-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automatically scans your codebase for critical security vulnerabilities, helping to prevent breaches and protect sensitive data.

Core Features & Use Cases

  • Vulnerability Detection: Identifies hardcoded secrets, SQL injection risks, XSS flaws, insecure dependencies, and missing input validation.
  • Severity Assessment: Assigns a severity level (Critical, High, Medium, Low) to each finding.
  • Use Case: Before deploying a new feature, run this Skill to ensure no API keys are accidentally committed and that user inputs are properly validated, preventing common attack vectors.

Quick Start

Run the ln-621-security-auditor skill to scan the codebase located at /path/to/your/codebase.

Frequently Asked Questions about ln-621-security-auditor

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

FAQPage Schema
How do I scan my codebase for hardcoded secrets and SQL injection vulnerabilities?

To scan a codebase for hardcoded secrets and SQL injection vulnerabilities, run the security auditor against your root directory. It automatically identifies these risks, assigns a severity level, and provides actionable remediation recommendations.

What is the best way to automate security audits before deploying a new feature?

Automating security audits before deployment involves running a code scanning worker in your pipeline. This process detects missing input validation and XSS flaws, returning a structured report with severity scores and compliance metrics.

Can I use automated code scanning to check for insecure dependencies in my tech stack?

Yes, automated code scanning can check for insecure dependencies within your tech stack. By processing the codebase root and stack information, the audit identifies vulnerable components and generates findings with location and effort estimates.

How does a security audit identify missing input validation across a codebase?

A security audit identifies missing input validation by analyzing codebase patterns against known attack vectors. It evaluates the source code structure, flags unprotected entry points, and outputs structured findings detailing the exact location and required effort.

Does the security auditor work as a standalone tool or within a coordinator pipeline?

The security auditor operates as a worker within a coordinator pipeline. It receives inputs like the codebase root and tech stack to process, generating a comprehensive security audit report with a compliance score rather than functioning as a standalone tool.