security-audit

Trace untrusted-source data to sinks across Go, Ruby, and Shell codebases.

2|Updated May 18, 2022
One-click install
npx skills add https://github.com/alexfalkowski/bin --skill security-audit-alexfalkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/alexfalkowski/bin/tree/main/skills/security-audit
Command: npx skills add https://github.com/alexfalkowski/bin --skill security-audit-alexfalkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, evidence-based framework for auditing code, scripts, and infrastructure to identify security vulnerabilities, unsafe patterns, and configuration gaps.

Core Features & Use Cases

  • Source-to-Sink Analysis: Traces data flow from untrusted inputs to dangerous sinks like shell execution or filesystem operations.
  • Language-Specific Guidance: Includes specialized audit references for Go, Ruby, and Shell environments to ensure context-aware security checks.
  • Use Case: Use this during a pull request review to verify that new shell scripts or Go HTTP handlers are not introducing command injection or credential leakage risks.

Quick Start

Use the security-audit skill to perform a comprehensive vulnerability review of the current repository changes.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I trace untrusted data flow to dangerous sinks during a code review?

To trace untrusted data flow during a code review, perform a source-to-sink analysis tracking inputs to dangerous sinks like shell execution. This identifies command injection and credential leakage risks by mapping data paths across the codebase.

Can I use this security audit to check Go HTTP handlers for vulnerabilities?

Yes, you can audit Go HTTP handlers for vulnerabilities using language-specific guidance. It applies context-aware security checks to Go environments to identify validation gaps and configuration errors in your code.

What is the best way to identify configuration errors and validation gaps in shell scripts?

The best way to identify configuration errors in shell scripts is a systematic security audit. It evaluates shell environments to detect unsafe patterns, configuration gaps, and validation vulnerabilities in your scripts.

How do I perform evidence-based risk assessment on new pull requests?

Perform evidence-based risk assessment on pull requests by auditing code changes for security vulnerabilities and unsafe patterns. This provides a structured framework to verify new commits do not introduce risks like command injection.

Does this vulnerability audit work with Ruby codebases?

Yes, this vulnerability audit works with Ruby codebases by applying specialized references. It ensures context-aware security checks to identify vulnerabilities and validation gaps specific to Ruby environments.

When do I need a systematic security audit for my repository?

You need a systematic security audit when verifying repository changes for compliance and hardening. It identifies vulnerabilities by tracing data flow from untrusted sources to dangerous sinks, satisfying evidence-based risk assessment requirements.