Phishing Simulation Analysis

Phishing Simulation Analysis is a skill for Claude Code from WYRE-AI/msp-claude-plugins. It costs 56 tokens per session (1,531 once invoked), scanned A, original, Apache-2.0.

A way to analyse controlled phishing tests across multiple campaigns, including the click-rate direction and people who click repeatedly. It can optionally compare these results with real phishing incidents, keeping simulated and real activity distinct.

In plain words
What is it for?
Use it to track phishing-test trends, identify repeat clickers, and relate simulation results to real-world phishing activity.
Why use it?
A single test result does not show whether behaviour is improving or identify persistent patterns. This analysis gives training teams evidence for deciding who needs targeted follow-up.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the awareness-pack plugin — 3 skills, 3 commands, 3 agents shipped together

Good fit Use it to track phishing-test trends, identify repeat clickers, and relate simulation results to real-world phishing activity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis
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 WYRE-AI/msp-claude-plugins --skill phishing-simulation-analysis
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install awareness-pack, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 3 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 Phishing Simulation Analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis/github.svg)](https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis)
Your own site
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis/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 Phishing Simulation Analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/phishing-simulation-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,531 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.00056 $0.01531
Opus 5 $0.00028 $0.00766
Sonnet 5 $0.00011 $0.00306
Haiku 4.5 $0.00006 $0.00153

Measured 5d ago against content hash 7cc34673e21a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

Phishing Simulation Analysis 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 5d 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.

msp-claude-plugins/awareness-pack/skills/phishing-simulation-analysis/SKILL.md · 152 lines

How it starts

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

Phishing Simulation Analysis

Overview

A phishing-simulation campaign is only as useful as the trend and pattern analysis built on top of its raw click data. A single campaign's click rate tells you almost nothing on its own; the trend across campaigns, and which specific users click repeatedly, are what actually drive training prioritization. This skill covers how to build that analysis across whatever simulation platform is connected, and how to optionally enrich it with real-world phishing-incident data when a technical security tool is also available — treating that enrichment as a bonus, never a requirement.

Anti-triggers

  • Building or sending a simulated campaign — templates, landing pages, recipient tracking, and phish-prone percentage are the vendor's surface; use knowbe4-phishing.
  • Real-world attack targeting rather than simulated tests — Very Attacked People reports and attack-index scoring describe genuine inbound campaigns; use proofpoint-people. This skill reasons about controlled tests, and never merges the two into one click rate.

Step Zero: Confirm What's Connected

Call conduit__search_tools for phishing-simulation and click-data tools before assuming a specific vendor. KnowBe4 is the primary simulation platform in this marketplace. Proofpoint (proofpoint__list_vap_users and related tools) and Checkpoint Avanan (avanan__list_threats and related tools) both carry phishing-click or "Very Attacked Person" style signal alongside their core email-security function — where connected, they are secondary/optional sources of real-world click and attack-targeting data, not replacements for a dedicated simulation platform's controlled test results. Simulated-click data (from a simulation platform) and real-click data (from an email-security tool) are different things; never merge them into one number without labeling which is which.

Key Concepts

Click-rate trend over time

Pull click rate per campaign, ordered chronologically, and report the trend direction (improving, flat, worsening) rather than a single snapshot number. A 12% click rate is meaningless without knowing whether last quarter's was 8% or 20%. Where the platform supports it, break the trend down by org and by training-module topic (e.g. invoice fraud vs. credential harvest) — a flat overall trend can hide a specific topic that's getting worse.

Read the full file on GitHub · 152 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. 5d ago First seen · 152 lines · 56 tokens per session scan A 7cc34673e21a

Subscribe to this mod's changes

Phishing Simulation Analysis is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,531 once invoked, about $0.0003 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.