red-team
Use when the user wants to adversarially stress-test a guardrail, classifier, prompt, or API they own or are authorized to test, to surface the distinct ways it fails. Generates adversarial inputs, runs them through the target and a ground-truth oracle, logs every target-vs-oracle disagreement as a failure de-duplicated by technique class, and loops until rounds stop surfacing new classes. Produces a catalogue of distinct, reproducible failures — the attacker half of a find→fix setup. Not for patching the target, and not for attacking systems the user does not own or have permission to test.
npx skills add gaasher/Agent-Loop-Skills --skill red-team --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Red Team An adversarial loop-until-dry. The artifact is a target system; the feedback signal is the count of **distinct failure classes** you can surface. Each round you craft adversarial inputs aimed at *new* weaknesses and run them through the target and a ground-truth **oracle** via `tools/harness.py`, which records every disagreement as a failure and de-dupes by the `class` (technique) you label each input with. You loop until fresh rounds stop finding anything new. This is only the *find* half of a find→fix setup: it catalogues failures and never patches the target (see [Pairing](#pairing)). ## When to use Use to harden a guardrail, classifier, content filter, prompt, or API that the user owns or is explicitly authorized to test — when the goal is a catalogue of distinct, reproducible failures, each an objective target-vs-oracle disagreement. A failure is a **bypass** (target allows what the oracle would block) or an **over-block** (target blocks what the oracle would allow). Default: drive the loop with a runnable oracle so the signal is objective. Escape hatch: if the user has no runnable oracle, the oracle is *your* judgment against a written policy — apply it consistentl
- When to use
- Setup
- The loop
- Ledger
- Constraints
- Pairing
What does the red-team skill do?
Use when the user wants to adversarially stress-test a guardrail, classifier, prompt, or API they own or are authorized to test, to surface the distinct ways it fails. Generates adversarial inputs, runs them through the target and a ground-truth oracle, logs every target-vs-oracle disagreement as a failure de-duplicated by technique class, and loops until rounds stop surfacing new classes. Produces a catalogue of distinct, reproducible failures — the attacker half of a find→fix setup. Not for patching the target, and not for attacking systems the user does not own or have permission to test.
How do I install it?
Run `npx skills add gaasher/Agent-Loop-Skills --skill red-team --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gaasher/Agent-Loop-Skills, a repository with 146 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.