analyzing-cyber-kill-chain

analyzing-cyber-kill-chain is a skill for Claude Code, Codex from Youngmaidainon/Agent-Level-Up. It costs 99 tokens per session (1,619 once invoked), scanned A, a copy of analyzing-cyber-kill-chain, MIT.

An incident-analysis method based on the Lockheed Martin Cyber Kill Chain, a seven-stage model of how cyberattacks can progress from information gathering to achieving their objective.

In plain words
What is it for?
It helps map observed attacker actions to attack stages, support post-incident reports, and plan prevention controls. It works alongside MITRE ATT&CK for more detailed technique mapping.
Why use it?
It helps show how far an attacker got, where defenses stopped the attack, and where earlier safeguards could have interrupted it.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps map observed attacker actions to attack stages, support post-incident reports, and plan prevention controls. It works alongside MITRE ATT&CK for more detailed technique mapping.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain
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.

Any agent
npx skills add Youngmaidainon/Agent-Level-Up --skill analyzing-cyber-kill-chain
Clone the repo
git clone --depth 1 https://github.com/Youngmaidainon/Agent-Level-Up

Made for: Claude Code, Codex.

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 analyzing-cyber-kill-chain

README.md
[![agentmods](https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain/github.svg)](https://agentmods.dev/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain)
Your own site
<a href="https://agentmods.dev/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain/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 analyzing-cyber-kill-chain

Your own site · 80×15
<a href="https://agentmods.dev/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain"><img src="https://agentmods.dev/badge/skills/youngmaidainon/agent-level-up/analyzing-cyber-kill-chain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,619 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 100% copy Near-identical to another mod 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.00099 $0.01619
Opus 5 $0.00049 $0.00809
Sonnet 5 $0.00020 $0.00324
Haiku 4.5 $0.00010 $0.00162

Measured 9d ago against content hash 6ed56459c6dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

analyzing-cyber-kill-chain 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 9d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/agent.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

100% identical to analyzing-cyber-kill-chain — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cyber-security/ctf/analyzing-cyber-kill-chain/SKILL.md · 149 lines

How it starts

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

Analyzing Cyber Kill Chain

When to Use

Use this skill when:

  • Conducting post-incident analysis to determine how far an adversary progressed through an attack sequence
  • Designing layered defensive controls with the goal of interrupting attacks at the earliest possible phase
  • Producing threat intelligence reports that communicate attack progression to non-technical stakeholders

Do not use this skill as a standalone framework — combine with MITRE ATT&CK for technique-level granularity beyond what the 7-phase kill chain provides.

Prerequisites

  • Complete incident timeline with forensic artifacts mapped to specific adversary actions
  • MITRE ATT&CK Enterprise matrix for technique-level mapping within each kill chain phase
  • Access to threat intelligence on the suspected adversary group's typical kill chain progression
  • Post-incident report or IR timeline from responding team

Workflow

Step 1: Map Observed Actions to Kill Chain Phases

The Lockheed Martin Cyber Kill Chain consists of seven phases. Map all observed adversary actions:

Phase 1 - Reconnaissance: Adversary gathers target information before attack.

  • Indicators: DNS queries from adversary IP, LinkedIn scraping, job posting analysis, Shodan scans of organization infrastructure

Phase 2 - Weaponization: Adversary creates attack tool (malware + exploit).

  • Indicators: Malware compilation timestamps, exploit document metadata, builder artifacts in malware samples

Phase 3 - Delivery: Adversary transmits weapon to target.

  • Indicators: Phishing emails, malicious attachments, drive-by downloads, USB drops, supply chain compromise

Phase 4 - Exploitation: Adversary exploits vulnerability to execute code.

  • Indicators: CVE exploitation events in application/OS logs, memory corruption artifacts, shellcode execution

Phase 5 - Installation: Adversary establishes persistence on target.

  • Indicators: New scheduled tasks, registry run keys, service installation, web shells, bootkits

Read the full file on GitHub · 149 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 149 lines · 99 tokens per session scan A 6ed56459c6dc

Subscribe to this mod's changes

analyzing-cyber-kill-chain is a skill published in the GitHub repository Youngmaidainon/Agent-Level-Up (3 stars, last pushed 14d ago), licensed MIT. It adds 99 tokens to every session and 1,619 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyzing-cyber-kill-chain, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

analyzing-cyber-kill-chain

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused…

marysatasselshaped667/skills-collection-1 · 99 tokens

analyzing-cyber-kill-chain

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused…

mukul975/Anthropic-Cybersecurity-Skills · 99 tokens

analyzing-cyber-kill-chain

Use when analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building…

oyi77/1ai-skills · 75 tokens

analyzing-cyber-kill-chain

A framework for analyzing an intrusion through the seven stages of the Lockheed Martin Cyber Kill Chain, from reconnaissance to the attacker’s final objective.

killvxk/cybersecurity-skills-zh · 85 tokens

analyzing-cyber-kill-chain

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused…

26zl/cybersec-toolkit · 99 tokens

analyzing-cyber-kill-chain

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused…

plurigrid/asi · 99 tokens