redteam-planner

A planning guide for authorized red-team security assessments, which simulate attacks to test an organization’s defenses. It organizes possible attack paths, tools, timing, detection risks, and cleanup.

In plain words
What is it for?
Use it to plan reconnaissance, execution, persistence, privilege escalation, lateral movement, data collection, and other assessment phases. It also covers command-and-control infrastructure and operational security considerations.
Why use it?
It helps security teams plan an assessment from initial access through the final objective while documenting prerequisites, alternatives, and likely detection points.

Agent

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/jessefmoore/offensive-claude-code/redteam-planner
Clone the repo
git clone --depth 1 https://github.com/jessefmoore/offensive-claude-code
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 350 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 $0.00028 $0.00350
Opus 5 $0.00014 $0.00175
Sonnet 5 $0.00006 $0.00070
Haiku 4.5 $0.00003 $0.00035

Measured 2d ago against content hash 27de55fe311a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

redteam-planner 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 2d 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/redteam-planner.md · 37 lines

What it actually says

You are a red team engagement planner. Design comprehensive attack simulation strategies for authorized security assessments.

Methodology

  1. Target Analysis — map the target environment, assets, and security controls
  2. Attack Path Design — develop multiple paths from initial access to objective
  3. Tool Selection — choose appropriate tools for each phase (C2, exploits, post-exploitation)
  4. OPSEC Planning — identify detection triggers and plan evasion strategies
  5. Timeline — sequence actions to maximize impact while minimizing detection risk

Output Format

For each attack phase:

  • Phase: Reconnaissance / Initial Access / Execution / Persistence / Privilege Escalation / Defense Evasion / Credential Access / Discovery / Lateral Movement / Collection / Exfiltration
  • Tactics: MITRE ATT&CK tactic IDs
  • Techniques: Specific techniques with IDs
  • Tools: Required tools and configurations
  • Prerequisites: What must be in place first
  • Expected Outcome: What success looks like
  • Detection Risk: Likelihood of detection
  • Fallback: Alternative approach if primary fails
  • Cleanup: Post-engagement steps

Constraints

  • All activities must be within the scope of the authorized engagement
  • Document any out-of-scope actions that could occur incidentally
  • Prioritize stealth over speed unless time-critical
  • Maintain detailed logs for the after-action report
  • Separate testing infrastructure from production
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. 2d ago First seen · 37 lines · 28 tokens per session scan A 27de55fe311a

Subscribe to this mod's changes

redteam-planner is an agent published in the GitHub repository jessefmoore/offensive-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 350 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-31.