security-reviewer

Trace untrusted input paths to harmful sinks in code changes.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill security-reviewer-ylxmf2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-reviewer
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/security-reviewer
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill security-reviewer-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps security reviewers identify and articulate exploitable paths in code changes, ensuring security gaps are caught before deployment.

Core Features & Use Cases

  • Threat-hunting across code changes and API surfaces to identify untrusted input paths and dangerous sinks.
  • Structured evidence gathering that maps entry points, unguarded boundaries, and mitigation opportunities.
  • Collaboration aids for security and development teams by documenting findings and recommended minimal fixes.

Quick Start

Provide a security review for a code change by tracing untrusted input from entry points to sinks and recommending the minimal boundary fix.

Frequently Asked Questions about security-reviewer

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

FAQPage Schema
How do I trace untrusted input paths to dangerous sinks during a code review?

Trace untrusted input from public endpoints to harmful sinks by mapping entry points and unguarded boundaries. This identifies exploitable attack paths in code changes, providing evidence-based findings for systematic threat-hunting.

What is the best way to identify security vulnerabilities before deploying code changes?

Identify security vulnerabilities in code changes by tracing untrusted input paths to harmful sinks. This approach ensures systematic threat-hunting across API surfaces, documenting findings and recommending minimal boundary-focused fixes before deployment.

When do I need to perform a security review for untrusted input and attack paths?

Perform a security review when changes touch public endpoints, permissions, or secret handling. The process maps untrusted input entry points to dangerous sinks, ensuring exploitable paths are caught during design reviews and security gating.

How do I provide a security review that recommends minimal boundary fixes?

Provide a security review by tracing untrusted input from entry points to sinks and recommending the minimal boundary fix. This structured evidence gathering maps unguarded boundaries and mitigation opportunities for development teams.

Does this security review approach work for design reviews and security gating?

This security review approach works for code reviews, design reviews, and security gating. It traces untrusted input paths to harmful sinks, satisfying requirements for systematic threat-hunting and evidence-based findings across API surfaces.

Can I use this method to document security findings and recommended fixes for developers?

You can use this method to document findings and recommended minimal fixes for development teams. It aids collaboration by gathering structured evidence that maps entry points, unguarded boundaries, and mitigation opportunities.