adversarial-review

Name: adversarial-review
Availability: InStock
Author: hiddink-ai

Map trust boundaries and attack surfaces in source code using STRIDE and OWASP.

1|Updated May 21, 2026

Search Tags:#code review #security #owasp #vulnerability assessment #threat modeling #stride

Ready to run

npx skills add https://github.com/hiddink-ai/hiddink-harness --skill adversarial-review-hiddink-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/adversarial-review
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill adversarial-review-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the gap between functional code reviews and security-focused auditing by identifying logic flaws and architectural vulnerabilities that static analysis tools often overlook.

Core Features & Use Cases

Multi-Phase Auditing: Executes a structured 4-phase review covering trust boundaries, attack surfaces, business logic, and defense mechanisms.
Attacker Mindset: Applies STRIDE and OWASP frameworks to simulate real-world exploitation scenarios against your codebase.
Use Case: Use this skill before a major release to identify potential privilege escalation or information disclosure risks in new API endpoints or authentication flows.

Quick Start

Run the adversarial review skill on the current directory using the thorough depth mode to perform a comprehensive security audit.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema

How do I perform an adversarial code review to find business logic flaws?▼

Adversarial code review identifies business logic flaws by mapping trust boundaries and attack surfaces, applying STRIDE and OWASP methodologies to simulate real-world exploitation scenarios against your source code directories.

What is threat modeling using STRIDE for source code security analysis?▼

STRIDE threat modeling for source code security systematically evaluates spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege risks across your application architecture and API endpoints.

Does adversarial security review require integrating static analysis tools like CodeQL?▼

Adversarial security review requires integration with security-focused tools like CodeQL or CRG to provide high-precision threat modeling and exploitation analysis beyond standard static analysis capabilities.

Can I use this approach to audit new API endpoints before a major release?▼

You can use adversarial security analysis before major releases to identify potential privilege escalation or information disclosure risks in new API endpoints and authentication flows through a structured 4-phase review.

What is the best way to find architectural vulnerabilities that static analysis tools overlook?▼

Adversarial code reviews bridge the gap between functional reviews and security auditing by applying attacker logic to evaluate defense mechanisms and uncover architectural vulnerabilities that static analysis often misses.