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]
tools
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
data-ai
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
testing
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
development
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.