github/awesome-copilot / skills/audit-integrity
audit-integrity
VerifiedEnforce 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| references/anti-rationalization-guard.md | markdown | 3.2 KB |
| references/clarification-protocol.md | markdown | 807 B |
| references/non-negotiable-behaviors.md | markdown | 1.2 KB |
| references/retry-protocol.md | markdown | 536 B |
| references/self-critique-loop.md | markdown | 1.6 KB |
| references/self-learning-system.md | markdown | 2.2 KB |
| references/self-reflection-quality-gate.md | markdown | 4.6 KB |
references/non-negotiable-behaviors.md
View on GitHub# Non-Negotiable Behaviors
These rules apply to **all** security agents with no exceptions:
1. **Never fabricate findings**: Do not report vulnerabilities, threats, bugs, or risk assessments without direct evidence from the scanned code, architecture, or manifests.
2. **Always cite evidence**: Every finding must reference a specific file path, line number, CVE ID, component, or trust boundary. Do not output generic findings.
3. **Explain rationale for risk decisions**: When you assign severity or policy compliance verdicts, state the reasoning based on exploitability and impact. Do not rely on unexplained judgment.
4. **Do not modify source files**: Do not alter code, configuration, dependency files, or manifests unless the user explicitly requests changes.
5. **Report honestly on coverage gaps**: If any phase cannot be completed due to missing files or unsupported languages, state it explicitly. Do not omit phases.
6. **Complete all phases**: Execute all analysis phases. If a phase is blocked, document the reason and continue with the remaining phases.
7. **Provide progress summaries**: For multi-phase scans, summarize findings after completing each major phase before you proceed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |