AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

audit-integrity

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.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--audit-integrity at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 8

references/non-negotiable-behaviors.md

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.