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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/commands/hermeticormus/libresecops-claude-code/attack-map)<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.
<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>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.00041 | $0.01021 |
| Opus 5.5 | $0.00016 | $0.00408 |
| Sonnet 5.5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
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.
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
-
Threat Intelligence Gathering: Collect publicly available intelligence on the specified threat actor or attack pattern from MITRE CTI, vendor reports, and CISA advisories.
-
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).
-
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)
-
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
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.
- 12d ago Changed · +5 lines · +41 tokens per session 771f2fdf5b8a
- 1mo ago First seen · 99 lines · 0 tokens per session scan A 24d254279883
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.
Other commands, from other repositories
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.