cash-audit

Analyze git diffs for security vulnerabilities through adversarial simulation.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cash-audit
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-audit
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies security vulnerabilities, dangerous defaults, and API design flaws in code changes before they reach production, preventing common developer pitfalls.

Core Features & Use Cases

  • Parallel Adversarial Analysis: Simultaneously evaluates code from the perspectives of a malicious attacker, a lazy developer, and a confused developer.
  • Discipline Mode: Provides a real-time checklist during implementation to ensure secure API design and configuration.
  • Use Case: Use this skill during a pull request review to automatically detect if a new configuration option introduces a security cliff or if an API parameter is susceptible to type confusion.

Quick Start

Run the cash-audit skill to perform a full security analysis on the current git diff.

Frequently Asked Questions about cash-audit

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

FAQPage Schema
How do I automate security audits for code changes in a pull request?

Automated security auditing analyzes source code changes for vulnerabilities like dangerous defaults and type confusion. It runs on the current git diff to detect security cliffs or API flaws during pull request reviews.

What is adversarial simulation in static code analysis?

Adversarial simulation in static analysis evaluates code simultaneously from attacker, lazy developer, and confused developer perspectives. This parallel approach identifies silent failures and insecure API design flaws before deployment.

How do I check my git diff for dangerous defaults and type confusion vulnerabilities?

Checking a git diff for type confusion and dangerous defaults requires running a local CLI bootstrap to execute security-focused code reviews. This process enforces secure coding patterns across the detected changes.

Does automated code review work with git integration to detect API design flaws?

Automated code review requires git integration to detect API design flaws and dangerous configuration options. The local CLI bootstrap operates directly on the current git diff to enforce secure API design.

Can I enforce secure coding patterns during implementation with a real-time checklist?

Enforcing secure coding patterns during implementation uses a Discipline Mode checklist. This real-time feature ensures secure API design and configuration while actively writing the code.

What are the limitations of using static analysis for silent failure detection?

Static analysis for silent failure detection requires local CLI bootstrap and git integration. It focuses on preventing common developer pitfalls in code changes but does not replace runtime vulnerability testing.