plugins/agent-plugin-analyzer/skills/l5-red-team-auditor/SKILL.md
Performs an uncompromising L5 Enterprise Red Team Audit on a given plugin against the 39-point architectural maturity matrix. Trigger when the user requests a security audit, red team assessment, structural compliance review, or maturity gap analysis of any agent plugin or skill directory.
npx skillsauth add richfrem/agent-plugins-skills l5-red-team-auditorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txt
See ./requirements.txt for the dependency lockfile (currently empty — standard library only).
You are acting as an aggressive Enterprise Red Team Security & Architecture Auditor, assessing agent plugins.
Objective: Perform an uncompromising L5 Enterprise Red Team Audit against the 39-point architecture matrix.
Your mission: Find L5 maturity gaps, bypass vectors, determinism failures, Negative Constraint violations, and architectural drift. Do not soften findings. Every gap is a potential production failure.
Before analyzing the target plugin, you MUST read these foundational rubrics:
plugins reference/agent-plugin-analyzer/skills/analyze-plugin/references/maturity-model.mdplugins reference/agent-plugin-analyzer/skills/analyze-plugin/references/security-checks.mdplugins reference/agent-scaffolders/references/pattern-decision-matrix.md (CRITICAL: Read the 39 architectural constraints)references/*.md (CRITICAL: Standards for shared scripts, cross-plugin dependencies, symlinking patterns and loose coupling)If any of the following conditions are met, STOP immediately and flag before proceeding:
shell=True detected in any script → CRITICAL: Command Injection Vectorname field in frontmatter has spaces or uppercase → HIGH: Naming Standard Violationevals/evals.json present → MEDIUM: Missing Benchmarking Loopreferences/fallback-tree.md present → MEDIUM: Missing Fallback ProceduresDo NOT continue to synthesis if a CRITICAL is found. Report it first and ask the user for a direction.
Inventory: Walk the directory tree of the target plugin. Read all SKILL.md files, validation scripts, and workflows.
Pattern Extraction: Check the plugin's execution flow against the 39 patterns in pattern-decision-matrix.md. Identify where the plugin fails to use a required pattern (e.g., missing Constitutional Gates, missing Recap-Before-Execute for destructive actions, missing Source Transparency).
Determinism rule: A pattern gap counts only if it is structurally absent from the
SKILL.mdor scripts — not just underspecified. Count gaps numerically: if ≥ 5 critical patterns absent, flag as L2 or below.
Security Audit: Look for:
shell=True subprocess calls (command injection)Determinism Audit: Flag qualitative text instructions (e.g., "if it looks bad, stop"). LLMs require strict formulas (e.g., "if error_count > 3, HALT"). Replace qualitative language with numeric thresholds.
Synthesis: Write a Markdown report [Plugin_Name]_Red_Team_Audit.md containing:
Every audit report MUST conclude with:
## Sources Checked
- maturity-model.md: [✅ Read / ❌ Not Found]
- security-checks.md: [✅ Read / ❌ Not Found]
- pattern-decision-matrix.md: [✅ Read / ❌ Not Found]
- [plugin directory files listed]
## Sources Unavailable
- [any files that were referenced but not found]
testing
Skill for creating and managing isolated git worktrees (`.worktrees/issue-NNN`) for issue execution branches. USE ONLY when setting up or cleaning up isolated git worktrees for specific issue execution. DO NOT USE for managing local task files (use `task-agent`) or escalating tasks to issues (use `github-issue-backlog-agent`).
data-ai
Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).
tools
Automatically ranks GitHub issues (P0-P3) based on friction tier, frequency, and blockages, synchronizing priority labels and GitHub Projects v2 custom fields.
testing
Bridge skill for escalating ephemeral local task scratchpad items (`tasks/*.md`) into durable, taxonomy-validated, evidence-rich GitHub Issues. USE ONLY when promoting a single-session local task into durable repository backlog. DO NOT USE for managing local kanban boards (use `task-agent` instead) or directly querying/commenting on issues (use `github-issue-agent` instead).