Skip to content

github/awesome-copilot / skills/audit-integrity

audit-integrity

Verified

Enforce output quality, evidence verification, and quality gates across security audits. Use this skill when you perform SAST, SCA, threat modeling, or security code reviews. Use this skill to verify code locations and taint traces for all findings. Use this skill to prevent the suppression of valid security findings. Use this skill to evaluate reports against quality thresholds (score ≥ 8/10) before delivery.

references/anti-rationalization-guard.md

View on GitHub
# Anti-Rationalization Guard

These rationalizations are **never** valid reasons to skip, omit, or downgrade findings:

## Universal Rationalizations

| If you think...                            | Mandatory response                                                                                                            |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| "No issues or threats found on first pass" | Systematic evaluation across all categories is required before you conclude clean. Expand scope and complete the full matrix. |
| "This looks fine, skip deep analysis"      | "Looks fine" is not evidence. Evidence is a code trace, architecture reference, or rule match. Run checks.                    |
| "The risk is probably lower in practice"   | Risk level is based on impact multiplied by likelihood. Justify any downgrade with explicit evidence.                         |
| "This is a false positive"                 | Flag the finding as a potential false positive, but include it. Do not silently suppress findings. Document the rationale.    |
| "This is outside scope"                    | State explicitly why, with a reference to the declared scope or assessment boundary.                                          |
| "No controls or mitigations needed here"   | State "No gap identified — rationale: [X]" explicitly. Silence is not assurance.                                              |

## SAST/SCA

| If you think...                          | Mandatory response                                                                                          |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| "SCA CVE is not exploitable here"        | Include the CVE with a documented context note. Do not silently suppress.                                   |
| "This phase can be skipped"              | All phases are mandatory. Document any phase that you cannot complete due to missing inputs.                |
| "Severity should be lower given context" | Severity is based on CVSS or exploitability. Justify any downgrade with explicit evidence. Do not suppress. |

## Threat Modeling

| If you think...                                | Mandatory response                                                                                       |
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| "This threat is mitigated by the architecture" | Document the specific compensating control and verify that it is implemented. Do not assume.             |
| "This category has no applicable threats here" | State "No applicable threats identified — rationale: [X]" explicitly. Do not silently omit categories.   |
| "Lateral movement is unlikely here"            | Document the specific architectural control that prevents pivoting and verify that it is implemented.    |
| "This threat actor would not target this"      | Document the basis for that exclusion. You must always consider insider threats and supply chain actors. |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall