security-audit

Audits repository and live site for security, privacy, and data-protection issues with evidence-backed findings.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill security-audit-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill security-audit-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews of a full-stack repo and its live site are easy to do superficially: scanners get skipped, findings get reported without verification, and privacy posture is ignored. This Skill runs a disciplined, evidence-first sweep across dependencies, secrets, API routes, the AI chat layer, HTTP headers, CI/CD, and analytics, then reports verified findings without changing any code. ## Core Features & Use Cases - Dependency and secret scanning: Runs npm audit, secretlint, and full git-history greps for leaked keys, adapting when scanners like gitleaks or trivy are unavailable. - AI chat and API review: Checks the chat endpoint against the OWASP LLM Top 10, including prompt-injection defenses, rate-limit failure modes, output rendering, and PII retention. - Live verification: Confirms HTTP security headers against the actual production response and probes the chat endpoint with a small, bounded set of requests. - Use Case: Before a public launch, ask for a security audit to receive a private report ranking real risks (e.g., an unsalted IP hash in analytics logs) with concrete suggested fixes, plus a section crediting existing defenses. ## Quick Start Ask the assistant to run the security audit on this repository and live site, then review the private report of verified findings and suggested fixes.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I run a security audit on my Next.js site and repo?

Invoke the audit with a request like "run the security audit" or the /security-audit command. It scans dependencies and secrets, reviews API routes and the AI chat against the OWASP LLM Top 10, verifies live HTTP headers, and produces a private report of verified findings.

What does the security audit check in an AI chat endpoint?

It reviews input validation and size limits, rate-limiting failure modes, prompt-injection defenses, output rendering for unsafe HTML, and PII retention in exchange logs. It also verifies that tool layers only read already-published generated data.

Does the security audit fix the vulnerabilities it finds?

No, it is report-only by design. It describes each finding with evidence, realistic impact, and a concrete suggested fix, but applying any change requires a separate explicit request.

Can the audit run without scanners like gitleaks or trivy installed?

Yes. It probes for scanner binaries first and falls back to npm audit, npx secretlint, and git history greps, which need no installation. It only offers to download a standalone scanner with permission.

Is it safe to probe the live production site during an audit?

The live probing is light and bounded: a handful of requests to the chat endpoint for injection, rate-limit, and malformed-body checks. It stops as soon as rate limiting engages and makes no state-changing calls.