skills.rest
jlaws
jlawsCOMMUNITY
Explore all skills by this author →
GitHub

agent-security-reviewer

Identify security vulnerabilities, auth flaws, and secrets with severity labels.

2|Updated Jan 3, 2026
Search Tags:#authorization#security#authentication#secrets#vulnerabilities#code-review
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill agent-security-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-security-reviewer
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/agent-security-reviewer
Command: npx skills add https://github.com/jlaws/dotfiles --skill agent-security-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers identify and remediate security vulnerabilities, authentication and authorization flaws, and secrets exposure in codebases before deployment.

Core Features & Use Cases

  • Static security review: detect injection flaws, insecure data handling, and hard-coded credentials.
  • Auth and API review: assess authentication/authorization paths and API security.
  • Secrets discovery: flag exposed credentials in code and configuration files.
  • Use Case: Review a new feature module to uncover a hard-coded API key or secret.

Quick Start

Explain and review code for security flaws in a given project, then return findings with severity labels.

Frequently Asked Questions about agent-security-reviewer

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

FAQPage Schema
How do I review my code for security vulnerabilities and exposed secrets?▼

To review code for security vulnerabilities, the skill identifies injection flaws, insecure data handling, and hard-coded credentials, returning findings with file paths, line numbers, and severity labels.

What is static security analysis and how does it find authentication flaws?▼

Static security analysis assesses authentication and authorization paths without executing code, detecting hard-coded API keys, secrets in configuration files, and insecure API handlers.

Can I use this security review on code written in different languages and frameworks?▼

Yes, this security review applies to auth flows, API handlers, and data-handling code across various languages and frameworks to uncover vulnerabilities before deployment.

What is the best way to check for hard-coded credentials in a new feature module?▼

The best way to check for hard-coded credentials is running a static security review on the new feature module to flag exposed API keys and secrets in code and configuration files.

How are security vulnerabilities categorized when reviewing API handlers?▼

When reviewing API handlers, security vulnerabilities are categorized using severity labels: [critical], [high], [medium], and [low], alongside specific file paths and line numbers.

Related Skills

Explore More Software Engineering Skills→
devopstalesdevopstales
1

semgrep-security

Scan source code for security vulnerabilities and code quality issues with Semgrep.

Community
Intermediate
aakash-dharaakash-dhar

security-audit

Audit code for injection attacks, exposed secrets, and authentication flaws.

Community
Advanced
RB-chrismandichRB-chrismandich
1

api-security-guard

Detect API security changes and validate touched endpoints across backend frameworks.

Community
Intermediate
AnsteorraAnsteorra
6

security-audit

Perform static and dynamic security audits on the KMP application.

Official
Advanced