⚡ Workflows
Red-team / Blue-team
Strengthen quality/security with one team attacking assumptions (Red) and another defending/correcting (Blue).
Bundle files
📄ORCHESTRATION.md— Orchestration
1# ORCHESTRATION.md
2
3## Diagram
4
5 ┌──────────┐ ┌──────────┐
6 │ Blue │─── delivers v1 ──>│ Red │
7 │ Team │ │ Team │
8 └────┬─────┘ └────┬─────┘
9 │ │
10 │ v
11 │ ┌───────────┐
12 │ │ Attack / │
13 │ │ Test │
14 │ └─────┬─────┘
15 │ │
16 v v
17 ┌──────────┐ findings ┌───────────────┐
18 │ Blue │<─────────────│ Red Report │
19 │ Fixes │ │ (sev + evid.) │
20 └────┬─────┘ └───────────────┘
21 │
22 v
23 ┌──────────┐
24 │ Re-test │
25 │ + close │
26 └──────────┘
27
28## Workflow
29Red-team / Blue-team
30
31## Objective
32Strengthen quality/security with one team attacking assumptions (Red) and another defending/correcting (Blue).
33
34## Roles
35- **Blue Team:** designs and implements initial solution.
36- **Red Team:** looks for failures, abuse, bypass, and edge cases.
37- **Moderator:** decides severity and priority of fixes.
38
39## Protocol
401. Blue delivers v1 + assumptions.
412. Red executes battery of attacks/adversarial tests.
423. Red reports findings (severity + evidence).
434. Blue corrects and documents mitigations.
445. Red retests for closure.
45
46## Severity criteria
47- **Critical:** high risk of outage or compromise.
48- **High:** significant functional impact.
49- **Medium/Low:** improvements or incremental hardening.
50
51## Closure
52- List of closed findings
53- Explicitly accepted risks
54
Lines: 54 | Words: 187
Install
Copy bundle to your OpenClaw workspace.
curl -fsSL https://raw.githubusercontent.com/cerealskill/openclaw-agents/main/install.sh | bash -s workflow red-team-blue-team ENRate this agent
Loading...
Sign in to rate this agent
Includes
- ✓ ORCHESTRATION.md
Info
- Slug
- red-team-blue-team
- Lines
- 54
- Words
- 187