Menü
Red Team — Generative Adversarial Security Design
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Single-pass network health observation. Checks API liveness, namespace freshness, drift, computes Network Health Score.
Deep investigation of a single construct. Identity-reality drift, maintenance pattern, composition analysis.
Single-pass network health observation. Checks API liveness, namespace freshness, drift, computes Network Health Score.
Autonomous observation loop. Time-boxed cycles with ratcheting health score, commits findings to grimoires.
Synthesize observations into a readable network health report. Aggregates patterns and trends from observation cycles.
Single-pass coherence sense of an ARBITRARY estate (a registry/state pair). Resolves the read-command from operator-local estate-config, shells the estate's own doctor read-only, emits exactly the STATUS|SIGNAL|MISMATCH tile. Sense-only — never mutates the estate.
| name | red-team |
| description | Red Team — Generative Adversarial Security Design |
| role | review |
| effort | xhigh |
| disallowed-tools | ["NotebookEdit","Bash(git add *)","Bash(git commit *)","Bash(git push *)"] |
| capabilities | {"schema_version":1,"read_files":true,"search_code":true,"write_files":true,"execute_commands":false,"web_access":true,"user_interaction":false,"agent_spawn":false,"task_management":false} |
| cost-profile | heavy |
Use the Flatline Protocol's red team mode to generate creative attack scenarios against design documents. Produces structured attack scenarios with consensus classification and architectural counter-designs.
Estimated per invocation: $5–$15/standard run or $15–$30/deep run (see Cost Matrix)
External providers called: Claude Opus 4.7 (primary attacker), GPT-5.3-codex (cross-review dissent)
To cap spend: Set red_team.budgets.standard_max_tokens and hounfour.metering.budget.daily_micro_usd in .loa.config.yaml. Budget enforcement is active when hounfour.metering.enabled: true.
If cost is a concern: Run /loa setup — the wizard will guide you to a budget-appropriate configuration.
Pricing verified: 2026-04-15. Prices change — recheck before large commitments.
/red-team grimoires/loa/sdd.md
/red-team grimoires/loa/sdd.md --focus "agent-identity,token-gated-access"
/red-team grimoires/loa/sdd.md --mode quick
/red-team grimoires/loa/sdd.md --depth 2 --mode deep
/red-team --spec "Users authenticate via wallet signature and receive a JWT"
| Argument | Flag | Default | Description |
|---|---|---|---|
| document | positional | required | Path to document to red-team |
| spec | --spec | — | Inline spec text (creates temp document) |
| focus | --focus | all | Comma-separated attack surface categories |
| section | --section | all | Specific document section to target |
| depth | --depth | 1 | Attack-counter_design iterations |
| mode | --mode | standard | Execution mode: quick, standard, deep |
red_team.enabled: true in .loa.config.yaml--spec--focusflatline-orchestrator.sh --mode red-team| Mode | Models | Cross-Validation | Counter-Design | Budget |
|---|---|---|---|---|
| Quick | 2 (primary only) | Skip | Inline only | 50K tokens |
| Standard | 4 (primary + secondary) | Full | Full synthesis | 200K tokens |
| Deep | 4 + iteration | Full | Full + multi-depth | 500K tokens |
CONFIRMED_ATTACK — all findings are THEORETICAL or CREATIVE_ONLY| Category | Criteria | Meaning |
|---|---|---|
| CONFIRMED_ATTACK | Both models score >700 | Attack is realistic and should be addressed |
| THEORETICAL | One model >700, other ≤700 | Plausible but models disagree |
| CREATIVE_ONLY | Neither model scores >700 | Novel but neither model finds it convincing |
| DEFENDED | Both models >700 AND counter-design exists | Attack is real but already has effective defense |
Score Examples:
When any attack scores severity >800:
Interactive mode: Present attack details and require acknowledgment:
HUMAN REVIEW REQUIRED
ATK-003: Confused Deputy in Ensemble Routing
Severity: 920/1000
Consensus: CONFIRMED_ATTACK
[A]cknowledge / [D]ismiss / [E]scalate
Autonomous mode: Write to pending-review.json for later human review.
| File | Permissions | Content |
|---|---|---|
.run/red-team/rt-{id}-result.json | 0644 | Full JSON result |
.run/red-team/rt-{id}-report.md | 0600 | Full report (restricted) |
.run/red-team/rt-{id}-summary.md | 0644 | Safe summary for PR/CI |
.run/red-team/.ci-safe | 0644 | Manifest of CI-safe files |
| Error | Cause | Resolution |
|---|---|---|
| "red_team.enabled is not true" | Config toggle off | Set red_team.enabled: true |
| "Input blocked by sanitizer" | Credentials in document | Remove credentials from input |
| "Budget exceeded" | Token limit hit | Use lower execution mode |
| "Orchestrator failed" | Model invocation error | Check API keys, retry |
red_team:
enabled: true
mode: standard
thresholds:
confirmed_attack: 700
theoretical: 400
human_review_gate: 800
budgets:
quick_max_tokens: 50000
standard_max_tokens: 200000
deep_max_tokens: 500000
When red_team.simstim.auto_trigger: true, the red team automatically runs as Phase 4.5 (RED TEAM SDD) during the simstim workflow, after FLATLINE SDD review and before PLANNING.
/flatline-review — Standard Flatline Protocol quality review/audit — Codebase security audit (implementation-level).claude/data/attack-surfaces.yaml — Attack surface registry.claude/data/red-team-golden-set.json — Calibration corpus