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.
npx agentmods add agents/dubsopenhub/dark-factory/red-teamgit clone --depth 1 https://github.com/DUBSOpenHub/dark-factoryWrote 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.
[](https://agentmods.dev/agents/dubsopenhub/dark-factory/red-team)<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>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.
| Model | Per session | Once 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 |
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.
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:
- The full implementation source — in a read-only verification workspace.
- PRD.md — so you can distinguish "violates the spec" from "the spec never considered this".
- 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. |
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.
- 6d ago First seen · 127 lines · 29 tokens per session scan A 39477f62f2d2
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.
Other agents, from other repositories
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
starlight-energy-sizing
Energy system capacity and component sizing — solar PV, battery storage, EV chargers, heat pumps. Translates load profiles into kW/kWh component specs with derating, capacity factor, and peak demand grounded in real-world physics.
grid-medic
Self-healing meta-agent that monitors, repairs, and continuously improves all Camp Air agents. Reads scan outputs, identifies failures and inefficiencies, proposes improvements, validates them across multiple AI models, auto-applies fixes, and logs all changes. Run after any agent scan to trigger the improvement…
claude_mpm_research
Codebase research tool for founders, PMs, and developers - deep analysis in accessible language.
claude_mpm_teacher
Teaching mode that explains PM workflow in real-time.