analyzing-cyber-kill-chain

analyzing-cyber-kill-chain is a skill for Claude Code from oyi77/1ai-skills. It costs 75 tokens per session (998 once invoked), scanned A, original, MIT.

A guide for mapping an intrusion against the Cyber Kill Chain, a seven-stage model of how attacks progress from preparation to achieving their goal. It shows which stages the attacker reached and where defenses interrupted the sequence.

In plain words
What is it for?
Use it for post-incident reviews, defensive-control planning, and reports that explain attack progress to non-technical stakeholders.
Why use it?
Incident reports often contain many separate events without a clear overall progression. A shared attack model helps identify failed controls and earlier points where the attack could have been stopped.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit Use it for post-incident reviews, defensive-control planning, and reports that explain attack progress to non-technical stakeholders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/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 oyi77/1ai-skills --skill analyzing-cyber-kill-chain
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

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/oyi77/1ai-skills/analyzing-cyber-kill-chain/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-cyber-kill-chain)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-cyber-kill-chain"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/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/oyi77/1ai-skills/analyzing-cyber-kill-chain"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-cyber-kill-chain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 998 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00075 $0.00998
Opus 5 $0.00037 $0.00499
Sonnet 5 $0.00015 $0.00200
Haiku 4.5 $0.00007 $0.00100

Measured 7d ago against content hash 92ccdc5e8e8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 7d 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.

cybersecurity/analyzing-cyber-kill-chain/SKILL.md · 116 lines

How it starts

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

Analyzing Cyber Kill Chain

Overview

Cybersecurity skill for analyzing cyber kill chain. Follows industry best practices and security standards.

When to Use

Trigger phrases:

  • "analyzing cyber kill chain"
  • "Conducting post-incident analysis to determine how far an adversary progressed t"
  • "Designing layered defensive controls with the goal of interrupting attacks at th"
  • "Producing threat intelligence reports that communicate attack progression to non"

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.

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

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

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
  1. Scope the Analysis — Define what cyber kill chain artifacts or data sources to examine and the investigation timeline.
  2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
  3. Extract Key Indicators — Parse and extract relevant cyber kill chain data points from collected artifacts.
  4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
  5. Build Timeline — Construct a chronological sequence of events related to cyber kill chain.
  6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Read the full file on GitHub · 116 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. 7d ago First seen · 116 lines · 75 tokens per session scan A 92ccdc5e8e8d

Subscribe to this mod's changes

analyzing-cyber-kill-chain is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 998 once invoked, about $0.0004 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-09-04.

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…

mukul975/Anthropic-Cybersecurity-Skills · 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…

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…

pinkpixel-dev/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…

Mikaru0Mystic/sectinel · 99 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…

plurigrid/asi · 99 tokens