Skip to content
cccskills
FreePublished on GitHub

audit-integrity

Check security audit findings against code evidence and trace how untrusted input moves through a system. Guide a second review, document verification gaps, and assess draft reports against a minimum quality score before delivery.

OriginalShow the original description

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.

See how to install

Good for

  • Verifying evidence behind security review findings
  • Rechecking input flows after an initial analysis
  • Assessing report quality before delivery
  • Recording lessons from a completed audit

Files included (8)

  • SKILL.md3.9 KB
  • references/anti-rationalization-guard.md3.2 KB
  • references/clarification-protocol.md807 B
  • references/non-negotiable-behaviors.md1.2 KB
  • references/retry-protocol.md536 B
  • references/self-critique-loop.md1.6 KB
  • references/self-learning-system.md2.2 KB
  • references/self-reflection-quality-gate.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Audit Integrity Skill

Enforce output quality, intellectual honesty, and continuous improvement across security audits and code reviews.

When to Use

  • Perform security analyses, threat models, code reviews, or quality audits.
  • Validate that every finding has verified code evidence and taint flow.
  • Prevent the suppression or rationalization of security findings.
  • Evaluate draft reports against the quality gate threshold (score ≥ 8/10).
  • Record lessons learned and security memories after you complete a scan.

Components

This skill provides 7 modular capabilities in the references/ directory. Load each file when you reach its execution phase:

ComponentReference FilePurpose
Clarification Protocolreferences/clarification-protocol.mdAsk a maximum of 2 targeted questions when scope is not clear
Anti-Rationalization Guardreferences/anti-rationalization-guard.mdProhibited rationalizations and mandatory responses for findings
Self-Critique Loopreferences/self-critique-loop.mdMandatory second pass to verify evidence and coverage
Retry Protocolreferences/retry-protocol.mdTool failure and empty search handling: retry once, then document
Non-Negotiable Behaviorsreferences/non-negotiable-behaviors.mdMandatory rules: do not fabricate, cite evidence, report gaps
Self-Reflection Quality Gatereferences/self-reflection-quality-gate.mdScoring rubric (1–10 scale) with a minimum threshold of 8
Self-Learning Systemreferences/self-learning-system.mdTemplates and rules for lessons and security memories

Execution Flow

Load reference files as you reach each phase:

  1. Before analysis: If scope or policy is not clear, read references/clarification-protocol.md. Ask a maximum of 2 targeted questions.
  2. During analysis: Follow references/non-negotiable-behaviors.md. At each triage decision, consult references/anti-rationalization-guard.md.
  3. On tool or search failure: Follow references/retry-protocol.md. Do not assume code is secure without verification.
  4. After initial analysis: Complete a second pass with the checklist in references/self-critique-loop.md. Verify taint traces and manifest coverage.
  5. Before delivery: Score the draft report using references/self-reflection-quality-gate.md. All categories must score ≥ 8.
  6. Final delivery: Record lessons and memories using references/self-learning-system.md.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot40.2KUpdated Oct 17, 2026

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot40.2KUpdated Oct 17, 2026

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot40.2KUpdated Oct 17, 2026

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot40.2KUpdated Oct 17, 2026

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot40.2KUpdated Oct 17, 2026

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot40.2KUpdated Oct 17, 2026

See all skills by github

Report a problem with this skill