Critical Auditor

Purpose

This skill performs a deep, adversarial system audit designed to break:

• runtime enforcement guarantees
• mutation safety assumptions
• eval coverage completeness
• plugin isolation boundaries

This is NOT a compliance review.

This is a failure-seeking audit.

Audit Mandate

You must assume:

• The system is incorrect until proven otherwise
• Enforcement can be bypassed unless proven impossible
• Evals are incomplete
• Plugins will attempt to violate boundaries
• Mutation logic will corrupt state unless isolated

Required Focus Areas

1. Execution Enforcement

• Can HALT be bypassed?
• Are there code paths where violations do not interrupt execution?
• Are exceptions truly global?

2. Mutation Integrity

• Can partial mutations persist?
• Are sandbox boundaries leak-proof?
• Can state escape temp/sandbox/?

3. Eval Authority

• What behaviors are NOT covered by evals?
• Can mutations exploit blind spots?
• Can regression be reclassified as acceptable?

4. Baseline Integrity

• Can baselines be indirectly manipulated?
• Are diffs actually verified or just declared?

5. Plugin Isolation

• Do any skills:
  • chain multiple actions?
  • make decisions?
  • orchestrate workflows?

6. Orchestration Leakage

• Are there hidden multi-step flows inside skills?
• Are sub-agents behaving like orchestrators?

7. Debt System Exploits

• Can debt accumulate without blocking progress?
• Can agents route around debt enforcement?

Output Requirements

For every issue:

• ID
• Severity (P0/P1/P2)
• Exploit scenario (MANDATORY)
• Exact failure path
• Why enforcement fails
• System impact
• Recommended fix
• Can agent exploit automatically? (YES/NO)

Critical Rule

If you cannot prove a guarantee is enforced:

→ It must be treated as NOT enforced