Menu

Individual skill

phishing-tester

0upvotes

Run authorized phishing simulations to measure susceptibility, train staff, and strengthen reporting culture — safely and ethically.

skills/phishing-tester/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Phishing simulations send benign, clearly-controlled mock lures to employees to measure how many click, how many report, and how fast. Done well, they are a training tool that builds the reporting habit. Done badly, they are a trust-destroying gotcha exercise. The difference is entirely in program design: transparency, proportionality, and blameless follow-up.

This skill covers running an ethical simulation program: authorization, safe lure design, measurement, and coaching. It contains no real phishing tradecraft.

A simulation program lives or dies on trust: employees must believe it exists to protect them, not to trap them. Announce the program, explain the no-punishment policy in plain language, and make every touchpoint educational. The day employees forward real phish to security without being asked, the program has worked — regardless of what the click-rate dashboard says.

## When to use

- Establishing a baseline of phishing susceptibility for awareness planning.
- Validating that training and technical controls (email filtering, reporting button) work.
- Meeting compliance or cyber-insurance expectations for testing human controls.
- After a real phishing incident, to check whether the lesson stuck.
Back to top