adversarial-tests

Identify code invariants and generate adversarial stress tests for security.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill adversarial-tests-kriscendobot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-tests
Source: https://github.com/kriscendobot/garden/tree/main/skills/adversarial-tests
Command: npx skills add https://github.com/kriscendobot/garden --skill adversarial-tests-kriscendobot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the gap between standard unit testing and robust security by systematically attacking code invariants to uncover hidden vulnerabilities and edge-case failures.

Core Features & Use Cases

  • Invariant Brainstorming: Provides a comprehensive checklist of adversarial inputs including boundary conditions, type confusion, and reentrancy issues.
  • Automated Sabotage: Integrates with the panel review process to simulate malicious or unexpected inputs that standard testing suites often overlook.
  • Use Case: When developing a new module, use this Skill to generate a suite of stress tests that verify how your code handles unexpected inputs like circular structures, frozen objects, or non-idempotent getters.

Quick Start

Ask the adversarial-tests skill to generate a set of invariant attacks for the current module to identify potential security regressions.

Frequently Asked Questions about adversarial-tests

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

FAQPage Schema
How do I stress-test code invariants against edge cases?

Adversarial testing targets code invariants by simulating malicious or unexpected inputs that standard testing suites overlook, uncovering hidden vulnerabilities and edge-case failures to bridge the gap between unit testing and robust security.

Can I use this to generate stress tests for boundary conditions and type confusion?

Yes, you can generate a suite of stress tests for boundary conditions and type confusion by asking the skill to simulate unexpected inputs like circular structures, frozen objects, or non-idempotent getters against your module.

Does this approach validate implementation contracts for failure modes?

Yes, validating implementation contracts is achieved by asserting specific failure modes and defensive coverage, ensuring your code handles unexpected inputs and maintains robustness against adversarial attacks.

What is the best way to test code robustness against circular structures and frozen objects?

The best way to test code robustness is to integrate automated sabotage into a panel review process, simulating malicious inputs like circular structures and frozen objects that standard testing suites often overlook.

When should I use adversarial testing instead of standard unit testing?

You should use adversarial testing when standard unit testing is insufficient to uncover hidden vulnerabilities, specifically when you need to systematically attack code invariants to ensure software robustness and security.