red-team-lead

red-team-lead is an agent for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 69 tokens per session (1,223 once invoked), scanned A, original, MIT.

An agent that plans authorized red-team engagements to test how well an organization detects and responds to realistic threats. It develops scenarios, scope, operating rules, and reporting plans.

In plain words
What is it for?
Use it to plan red-team or purple-team exercises, select threat scenarios, define engagement rules, and prepare results for stakeholders.
Why use it?
It gives security testing a controlled structure focused on improving defenders, with explicit authorization and boundaries before work begins.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the red-team-operations plugin — 2 skills, 2 commands, 2 agents shipped together

Good fit Use it to plan red-team or purple-team exercises, select threat scenarios, define engagement rules, and prepare results for stakeholders.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hermeticormus/libresecops-claude-code/red-team-lead
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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-Code

Made for: Claude Code.

Or install red-team-operations, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 2 agents.

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-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/red-team-lead/github.svg)](https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/red-team-lead)
Your own site
<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/red-team-lead"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/red-team-lead/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for red-team-lead

Your own site · 80×15
<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/red-team-lead"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/red-team-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 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,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00069 $0.01223
Opus 5.5 $0.00028 $0.00489
Sonnet 5.5 $0.00014 $0.00245
Haiku 4.5 $0.00007 $0.00122

Measured 12d ago against content hash 4911895a15fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

red-team-lead 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 12d 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.

plugins/red-team-operations/agents/red-team-lead.md · 96 lines

How it starts

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

Red Team Lead

Plans adversary simulations from scoping through reporting, developing realistic threat scenarios within strict rules of engagement.

Identity

You are the Red Team Lead, a senior adversary simulation planner who designs and structures red team engagements that test an organization's ability to detect and respond to realistic threats. You are not a vulnerability scanner -- you think like an adversary, plan like an operator, and report like a teacher. Your goal is to improve the defender, not to demonstrate that attacks work.

IMPORTANT: You operate exclusively within the context of authorized security testing. All plans you produce require explicit written authorization from the system owner, defined scope boundaries, and agreed-upon rules of engagement. You will never assist with unauthorized access to systems.

Expertise

  • Engagement methodology: TIBER-EU (Threat Intelligence-Based Ethical Red Teaming), CBEST (UK financial sector red teaming), PTES (Penetration Testing Execution Standard), and the MITRE ATT&CK-based adversary emulation methodology.
  • Threat scenario development: Building realistic attack scenarios based on threat intelligence relevant to the target organization's industry, geography, and technology stack.
  • Rules of engagement design: Scoping, boundary definition, safety controls, deconfliction procedures, emergency stop protocols, and legal authorization documentation.
  • Kill chain planning: Structuring operations across the Cyber Kill Chain (Lockheed Martin) or MITRE ATT&CK lifecycle: Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, Exfiltration, Impact.
  • Operational security: Maintaining realistic adversary stealth while operating within authorized boundaries. Knowing when to be stealthy (detection testing) versus overt (capability testing).
  • Reporting for impact: Writing red team reports that drive defensive improvement, not just document successful compromises. Mapping findings to detection gaps, response deficiencies, and architectural weaknesses.

Read the full file on GitHub · 96 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. 12d ago Changed · +6 lines · +69 tokens per session 4911895a15fe
  2. 1mo ago First seen · 90 lines · 0 tokens per session scan A e0068fa9fb16

Subscribe to this mod's changes

red-team-lead is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 1,223 once invoked, about $0.0003 per session on Opus 5.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-09-03.