security-audit

Audit codebases for security vulnerabilities across authentication, authorization, and dependencies.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill security-audit-g-zenr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/g-zenr/relay-api --skill security-audit-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for thorough security analysis of codebases, ensuring adherence to best practices and identifying potential vulnerabilities before they can be exploited.

Core Features & Use Cases

  • Comprehensive Checklist: Follows a detailed, multi-point audit checklist covering authentication, input validation, information leakage, audit trails, rate limiting, CORS, and dependencies.
  • Structured Findings: Organizes identified issues by severity (Critical, High, Medium, Low, Info) with specific file and line references.
  • Use Case: A development team can use this Skill to perform a pre-release security review of a new feature, ensuring all security requirements are met and potential risks are mitigated.

Quick Start

Perform a security audit of the codebase following Janet Moore's standards.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I perform a security audit on my codebase before release?

A codebase security audit checks for vulnerabilities in authentication, input validation, rate limiting, CORS, and dependencies. It follows a comprehensive checklist and provides findings grouped by severity with actionable remediation steps.

What does a deep code review for vulnerabilities cover?

A deep code review for vulnerabilities covers authentication, authorization, input validation, information leakage, audit trails, rate limiting, CORS, and dependencies to identify potential risks before they can be exploited.

How are security vulnerabilities grouped during a codebase audit?

Security vulnerabilities are grouped by severity—Critical, High, Medium, Low, and Info—during a codebase audit. Each finding includes specific file and line references to help development teams quickly locate and mitigate identified issues.

Can I use this security audit to check compliance and information leakage?

Yes, you can use this security audit to check compliance and information leakage. The audit systematically evaluates information leakage, audit trails, and adherence to best practices, ensuring all security requirements are met for a new feature.

What is the best way to identify rate limiting and CORS issues in my code?

The best way to identify rate limiting and CORS issues is to conduct a systematic security audit using a detailed checklist. This process detects these specific vulnerabilities and provides actionable remediation steps grouped by severity.