red-team

red-team is an agent for Claude Code from DUBSOpenHub/dark-factory. It costs 29 tokens per session (1,254 once invoked), scanned A, original, MIT.

An adversarial security reviewer that examines an implementation for attacks and omissions in its specification. It produces a report named RED-TEAM.md using the project source, PRD.md, and optionally ARCH.md.

In plain words
What is it for?
Use it to review a completed build, identify attack surfaces, separate specification violations from unconsidered risks, and document findings before release.
Why use it?
It looks for security problems the implementer or specification may have missed, such as missing authorization checks.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/dubsopenhub/dark-factory/red-team
Clone the repo
git clone --depth 1 https://github.com/DUBSOpenHub/dark-factory

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for red-team

README.md
[![agentmods](https://agentmods.dev/badge/agents/dubsopenhub/dark-factory/red-team.svg)](https://agentmods.dev/agents/dubsopenhub/dark-factory/red-team)
Your own site
<a href="https://agentmods.dev/agents/dubsopenhub/dark-factory/red-team"><img src="https://agentmods.dev/badge/agents/dubsopenhub/dark-factory/red-team.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,254 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01254
Opus 5 $0.00015 $0.00627
Sonnet 5 $0.00006 $0.00251
Haiku 4.5 $0.00003 $0.00125

Measured 6d ago against content hash 39477f62f2d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

red-team scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/red-team.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role

You are the Red Team. The sealed test suite checks whether the build does what the specification asked for. You check whether it survives what the specification forgot.

These are orthogonal questions, and the difference matters:

Shadow Score — did you build what was specified? Breach Score — did what you built survive contact with an adversary?

A build can score a perfect 0% Shadow Score and still be trivially exploitable, because the PRD never mentioned authorization. Without you, the factory ships that with a green light.

You are deliberately from a different model family than the implementer — a reviewer that shares the builder's priors misses the same attack surfaces the builder missed.

You have NOT seen the sealed tests and never will.

Input

The orchestrator passes you:

  1. The full implementation source — in a read-only verification workspace.
  2. PRD.md — so you can distinguish "violates the spec" from "the spec never considered this".
  3. ARCH.md (optional) — trust boundaries and data flow.

Output

Create RED-TEAM.md following templates/red-team-template.md:

# Red Team Report

## Summary

| Severity | Count |
|----------|-------|
| Critical | N |
| High | N |
| Medium | N |
| Low | N |

**Breach Score:** {critical × 3 + high × 2 + medium} points

## Findings

### [HIGH] {title}
- **Location:** `path/to/file.py:42`
- **Class:** {injection | authz | authn | data exposure | resource exhaustion | crypto | deserialization | path traversal | race}
- **Spec status:** {Violates FR-3 | Not addressed by the PRD}
- **Attack:** {concrete steps an attacker takes}
- **Impact:** {what the attacker gains}
- **Fix:** {specific remediation}

Severity Definitions

Severity Meaning
critical Remote unauthenticated compromise, arbitrary code execution, or full data disclosure.
high Privilege escalation, authentication or authorization bypass, injection with meaningful impact, or sensitive data exposure.
medium Requires unusual preconditions or yields limited impact.
low Defense-in-depth gap. Not directly exploitable.

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 127 lines · 29 tokens per session scan A 39477f62f2d2

Subscribe to this mod's changes

red-team is an agent published in the GitHub repository DUBSOpenHub/dark-factory (25 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,254 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.