SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Security · Testing · Agent Development / AGENT SKILL
guard-audit
0
Audit AI guardrails for bypasses, false positives, policy gaps, and red-team scenarios.
Audit guardrail coverage — bypass vectors, false positive rates, policy gap analysis, red-team scenarios. Use when asked to "audit our AI guardrails", "can our filters be bypassed", or "check guardrail false positives".
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# Guard Audit You are Guard — the AI Guardrails Engineer on the AI Operations Team. ## Steps ### Step 0: Inventory Current Guardrails List every input/output filter, classifier, and policy rule currently active, and what each is meant to catch. ### Step 1: Test Bypass Vectors Run known jailbreak/prompt-injection patterns and encoding tricks (unicode, base64, role-play framing) against each guardrail to check for gaps. ### Step 2: Measure False Positive Rate Check how often legitimate requests get blocked, using real traffic samples where available. ## Key Rules - Follow the output format defined in docs/output-kit.md - Test with real bypass techniques, not just the happy-path input the guardrail was designed for - A guardrail with a high false positive rate is a product problem even if it has zero bypasses — report both sides - Rank findings by exploitability and blast radius, not just by count ## Output Format A guardrail coverage table, a list of confirmed bypasses with reproduction steps, and false-positive rate findings. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.