Agent Skills: Protocol Enforcement (Red-Team Verification)

Standards for Red-Team verification and adversarial protocol audit. Use when verifying tasks, performing self-scans, or checking for protocol violations. Load as composite for all sessions. (triggers: verify done, protocol check, self-scan, pre-write audit, task complete, audit violations, retrospective, scan, red-team)

UncategorizedID: hoangnguyen0403/agent-skills-standard/common-protocol-enforcement

Install this agent skill to your local

pnpm dlx add-skill https://github.com/HoangNguyen0403/agent-skills-standard/tree/HEAD/.codex/skills/common/common-protocol-enforcement

Skill Files

Browse the full folder contents for common-protocol-enforcement.

Download Skill

Loading file tree…

.codex/skills/common/common-protocol-enforcement/SKILL.md

Skill Metadata

Name
common-protocol-enforcement
Description
Enforce Red-Team verification and adversarial protocol audit. Use when verifying tasks, performing self-scans, or checking for protocol violations. Load as composite for all sessions.

Protocol Enforcement (Red-Team Verification)

Priority: P0 (CRITICAL)

Red-Team Verification Protocol

Before declaring any task "done" or calling notify_user:

  1. Adversarial Audit: Search for Standard Defaults where project rules should exist.
  2. Protocol Check: Confirm active skills and workflows were loaded before writing.
  3. Evidence Check: Ask what command or artifact proves the completion claim.
  4. Execution Bias Check: Ask whether speed or convenience skipped a structural rule.

** Post-Write Self-Scan**

Immediately after tool call:

  • Scan: Read diff or file content.
  • Match: Check against Anti-Patterns in all active skills.
  • Fix: Re-edit immediately if violation detected.

Red Flags

  • Stop if "done" appears before fresh verification: No completion claim yet.
  • Stop if you relied on memory instead of re-reading files: Reload source of truth.
  • Stop if the shortcut is "small enough to skip protocol": Small changes hide drift.

Rationalization Prevention

  • "The change is tiny": Tiny changes still violate guardrails.
  • "The test passed earlier": Old evidence does not prove current state.
  • "I know the pattern already": Load the active skill anyway.

Anti-Patterns

  • No "Done" Bias: Functional success != Protocol success.
  • No Reliance on Memory: Always retrieval-led (Skill view_file) before write.
  • No Skipping Protocols: "Small changes" where most violations happen.

Execution Bias Detection

Look for:

  • Local mocks instead of shared fakes.
  • Hardcoded styles instead of design tokens.
  • Try-catch blocks without standard error handling.
  • Missing Pre-Write Audit Log in thoughts.

References

Protocol Enforcement (Red-Team Verification) Skill | Agent Skills