Installs into .claude/skills of the current project.
Are you the author of Red Team Stack?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-red-team-stack)
---
name: red-team-stack
description: Recommend a red-team tool stack and configuration for a given deployment. Use when you need help with red team stack.
license: CC-BY-NC-SA-4.0
phase: 18
lesson: 16
metadata:
version: 1.0.0
tags: [llama-guard, garak, pyrit, red-team-tooling, mlcommons-hazards]
---
Given a deployment description, recommend a red-team tool stack and regression cadence.
Produce:
1. Classifier placement. Recommend Llama Guard (3-8B, 3-1B-INT4, or 4-12B) at input, output, or both. For edge deployments, prefer 3-1B-INT4. For multimodal, Llama Guard 4.
2. Probe scanner configuration. Recommend Garak probes relevant to the deployment: hallucination (for RAG systems), data leakage (for PII-adjacent), prompt injection (always), jailbreaks (always). Specify the Prompt-Guard-86M + Llama-Guard-3-8B shield pairing for end-to-end evaluation.
3. Campaign orchestrator. Recommend PyRIT for pre-release campaigns on models with novel capabilities. Specify converter chains to run (paraphrase, encode, translate, roleplay) and orchestrator (Crescendo for escalation, TAP for branching).
4. Cadence. Garak nightly for regression. PyRIT per-release for deep red-teaming. Llama Guard deployed continuously.
5. Judge calibration. Specify the judge LLM (GPT-4-turbo, StrongREJECT, internal) for every tool that uses one. Judge calibration drives reported ASRs.
Hard rejects:
- Any deployment without at least one Llama Guard-class input or output classifier.
- Any release without Garak or equivalent single-turn regression.
- Any high-stakes deployment without a PyRIT-equivalent campaign before release.
Refusal rules:
- If the user asks for a single "best" tool, refuse — the three cover different layers and are layered, not substituted.
- If the user asks for an all-in-one commercial alternative, refuse the recommendation and point to the 2026 state: the three open tools are the current best-practice stack.
Output: a one-page recommendation that names the classifier placement, probe configuration, campaign orchestrator, regression cadence, and judge identity. Cite Meta (arXiv:2407.21783), NVIDIA Garak, and Microsoft PyRIT once each.
