security-review

Review code and agent configuration diffs for security vulnerabilities.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill security-review-t0lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/security-review
Command: npx skills add https://github.com/t0lab/harness-kit --skill security-review-t0lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Focused security reviews are frequently overlooked during general code review, leaving risky changes in authentication, authorization, secrets handling, shell execution, file/network boundaries, and agent configuration unexamined. This Skill narrows the scope to attacker-focused analysis so reviewers can determine whether a change enables access, code execution, data leakage, or unsafe agent behavior.

Core Features & Use Cases

  • Risk-driven checklist: Guides reviewers through authentication, authorization, secrets, injection, file/network boundaries, deserialization, and agent-specific risks.
  • Data-flow tracing: Emphasizes tracing attacker-controlled inputs to dangerous sinks with required validations and authorization checks.
  • Exploitability-focused findings: Produces concrete findings with severity, location, attacker input, exploit path, and remediation steps for developer triage.
  • Use Case: Run this review before merging PRs that touch auth flows, token handling, shell execution, file uploads, webhooks, MCP/hook config, or any code that handles PII or payments.

Quick Start

Review the diff for attacker-controlled inputs, trace each to its sinks, and produce exploitability-classified findings with locations, exploit paths, and recommended fixes.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a security review on a pull request that modifies authentication flows?

Perform a focused security review by applying a risk-driven checklist to the diff, tracing attacker-controlled inputs to dangerous sinks, and producing exploitability-classified findings with remediation steps for developer triage.

What is threat modeling for code changes and when do I need it?

Threat modeling for code changes is an attacker-focused analysis of diffs touching auth, secrets, or command execution. You need it before merging PRs that handle PII, payments, webhooks, or agent hooks to prevent security regressions.

How do I trace attacker-controlled inputs to find injection vulnerabilities in my diff?

Trace attacker-controlled inputs to dangerous sinks by reviewing the diff for required validations and authorization checks, ensuring every data-flow path is examined for injection, file, and network boundary risks.

Does this security review work for agent hooks and MCP configuration changes?

Yes, this security review works for agent hooks and MCP configuration changes, applying a risk-driven checklist to identify access control gaps, data leakage, and unsafe agent behavior before merge approval.

How do I classify the exploitability of vulnerabilities found during a code review?

Classify vulnerability exploitability by producing concrete findings that detail severity, precise location in the diff, attacker input vectors, the full exploit path, and actionable remediation guidance for developer triage.

What's the best way to prevent security regressions when handling secrets and shell execution?

The best way to prevent security regressions is running an attacker-focused diff review on changes to secrets handling and shell execution, verifying that all inputs are validated and proper authorization checks are enforced.