Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk…
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .claude/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .agents/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .cursor/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .gemini/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .github/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "investigating-phishing-email-incident" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/investigating-phishing-email-incident into .opencode/skills/investigating-phishing-email-incident/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-phishing-email-incident", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
investigating-phishing-email-incident
GitHub stars
34k
Token cost
~2.8k tokens
SKILL.md length
577 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0
At a glance
Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk…
Works in 6 steps: Extract and Analyze Email Headers → Analyze URLs and Attachments → Determine Campaign Scope → …
A reported phishing email requires full incident investigation to determine scope and impact
SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
Runs Python scripts from its folder; reaches urlscan.io and mb-api.abuse.ch
What it does
Investigating Phishing Email Incident is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).
It sits in Security. It works with Splunk, Microsoft Defender and Microsoft 365. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
A reported phishing email requires full incident investigation to determine scope and impact
Example prompts
“Use the investigating-phishing-email-incident skill to investigate phishing email incidents from initial user report through header analysis…”
“/investigating-phishing-email-incident”
Requirements
Python 3
A credential in YOUR_KEY
A credential in YOUR_VT_API_KEY
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
urlscan.io
mb-api.abuse.ch
graph.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Investigating Phishing Email Incident loads about 2.8k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 577 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~98
When it runs· the whole SKILL.md, loaded when a task matches
~2.8k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~3.5k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/investigating-phishing-email-incident/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
investigating-phishing-email-incident
description
Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.
Investigating Phishing Email Incident next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Investigating Phishing Email Incident compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Investigating Phishing Email Incident this skillmukul975/Anthropic-Cybersecurity-Skills
Guidance for cloud and SaaS security posture management - combining Defender for Cloud CSPM (IaaS/PaaS) and Defender for Cloud Apps SSPM (SaaS) to assess and harden posture across cloud and SaaS apps.
Guidance for Microsoft Defender XDR — the unified extended detection and response suite that correlates signals across endpoints, identities, email, and cloud apps into prioritised incidents with…
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Questions about Investigating Phishing Email Incident
What does Investigating Phishing Email Incident do?
Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk…. Investigating Phishing Email Incident is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms.
When should I use Investigating Phishing Email Incident?
Investigating Phishing Email Incident fits situations like: A reported phishing email requires full incident investigation to determine scope and impact.
How do I install Investigating Phishing Email Incident in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a claude-code`. Or copy the skill folder (skills/investigating-phishing-email-incident in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/investigating-phishing-email-incident in your project. Claude Code loads it when a task matches its description.
How do I install Investigating Phishing Email Incident in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a codex`. Or copy the skill folder (skills/investigating-phishing-email-incident in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/investigating-phishing-email-incident in your project. Codex loads it when a task matches its description.
Can I use Investigating Phishing Email Incident in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill investigating-phishing-email-incident -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-phishing-email-incident, .gemini/skills/investigating-phishing-email-incident, .github/skills/investigating-phishing-email-incident and .opencode/skills/investigating-phishing-email-incident in your project.
What does Investigating Phishing Email Incident need to run?
Going by SKILL.md and its folder, Investigating Phishing Email Incident needs Python for the scripts in its folder. Our summary lists: Python 3; A credential in YOUR_KEY; A credential in YOUR_VT_API_KEY.
Does Investigating Phishing Email Incident access the network?
SKILL.md names 3 domains. In commands or code: urlscan.io, mb-api.abuse.ch and graph.microsoft.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Investigating Phishing Email Incident safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Investigating Phishing Email Incident use?
Investigating Phishing Email Incident is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Investigating Phishing Email Incident use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 629 tokens, read only when the agent opens those files.
What are the alternatives to Investigating Phishing Email Incident?
Skills that share tags, products or a category with Investigating Phishing Email Incident: Cloud App Security Posture (vinayaklatthe/microsoft-security-skills, 175 stars), Sentinel (vinayaklatthe/microsoft-security-skills, 175 stars), Defender Xdr (vinayaklatthe/microsoft-security-skills, 175 stars) and AI Agent Activity (SCStelz/security-investigator, 249 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating Phishing Email Incident?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.