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/clarification-protocol.md
View on GitHub# Clarification Protocol
Before you start the analysis, pause and ask the user a maximum of **2 targeted questions** when:
- The system scope, asset boundary, or target module is ambiguous and you cannot infer it from the context
- A critical trust boundary or privilege tier is undefined
- The business context for impact prioritization or compliance framework selection is absent
- The programming language or framework cannot be detected from the workspace
**Rules:**
1. State your working assumptions explicitly and proceed.
2. Do not wait for confirmation unless the ambiguity alters the attack surface definition or trust boundary map.
3. Ask a maximum of 2 questions. If more ambiguity exists, document your assumptions and proceed.
4. If no ambiguity exists, proceed directly without questions.
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: 467k | 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: 467k | 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: 467k | 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: 193k | Updated | Claude CodeCodex | Verified | Install |