attack-map

attack-map is a command for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 41 tokens per session (1,021 once invoked), scanned A, original, MIT.

A defensive security command that maps a threat actor’s known behavior to MITRE ATT&CK, a catalog of real-world attack methods, and produces a checklist for validating detections.

In plain words
What is it for?
Use it to analyze threat intelligence, create detection checklists, prepare Atomic Red Team validation scenarios, or export an ATT&CK Navigator layer.
Why use it?
It turns threat reports or attack patterns into specific techniques that a security team can check and test. This helps reveal gaps in monitoring without carrying out an attack.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Good fit Use it to analyze threat intelligence, create detection checklists, prepare Atomic Red Team validation scenarios, or export an ATT&CK Navigator layer.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hermeticormus/libresecops-claude-code/attack-map
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 attack-map

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/attack-map/github.svg)](https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/attack-map)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/attack-map"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/attack-map/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 attack-map

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/attack-map"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/attack-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 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,021 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.00041 $0.01021
Opus 5.5 $0.00016 $0.00408
Sonnet 5.5 $0.00008 $0.00204
Haiku 4.5 $0.00004 $0.00102

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

Security

Grade A, and why

attack-map 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/commands/attack-map.md · 104 lines

How it starts

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

/attack-map

Map threat actor TTPs to MITRE ATT&CK techniques and generate a detection validation checklist.

Trigger

Use when you need to:

  • Map a known threat actor's behavior to ATT&CK for detection engineering
  • Analyze a threat intelligence report and extract actionable TTPs
  • Build a detection validation matrix for a specific adversary profile
  • Prepare atomic testing scenarios for blue team capability validation
  • Create an ATT&CK Navigator layer for a specific threat

NOTE: This command is for educational and defensive purposes -- building detections that catch these techniques.

Input

  • Required: One of the following:
    • A threat actor name or designation (e.g., "APT29", "FIN7", "Scattered Spider")
    • A threat intelligence report or advisory to analyze
    • A specific attack pattern or kill chain to map
  • Optional flag: --detection -- include detection rule stubs (Sigma format) for each technique
  • Optional flag: --atomic -- include Atomic Red Team test IDs for validation
  • Optional flag: --navigator -- output ATT&CK Navigator JSON layer

Process

  1. Threat Intelligence Gathering: Collect publicly available intelligence on the specified threat actor or attack pattern from MITRE CTI, vendor reports, and CISA advisories.

  2. TTP Extraction: Identify each tactic, technique, and procedure used by the adversary. Be specific -- extract sub-techniques (T1059.001 PowerShell, not just T1059 Command and Scripting Interpreter).

  3. ATT&CK Mapping: Map each TTP to the MITRE ATT&CK Enterprise matrix with:

    • Technique ID and name
    • The specific procedure (how the adversary uses this technique)
    • The tactic phase (where in the kill chain this occurs)
    • Confidence level (observed / assessed / inferred)
  4. Detection Requirements: For each technique, identify:

    • Required data sources (Sysmon events, Windows Event Log IDs, network flow data, cloud audit logs)
    • Detection logic (what pattern indicates this technique)
    • False positive considerations
    • Detection difficulty rating

Read the full file on GitHub · 104 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 · +5 lines · +41 tokens per session 771f2fdf5b8a
  2. 1mo ago First seen · 99 lines · 0 tokens per session scan A 24d254279883

Subscribe to this mod's changes

attack-map is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 1,021 once invoked, about $0.0002 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.