Individual skill
pretext-engineering
Design a credible phishing pretext and target shortlist from OSINT before any campaign is built — sender persona, scenario, timing, and the minimal target set.
packages/decepticon/decepticon/skills/standard/phisher/pretext-engineering/SKILL.md
Source commit df879550544d36b6b1e69062f05adae28537adf2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 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)
- 6,571
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- phishing Declared skill tag
- social-engineering Declared skill tag
- osint Declared skill tag
- pretext Declared skill tag
- engineering Derived category
- design Derived category
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,595 bytes
Read excerpt
# Pretext Engineering
The pretext is the campaign. A technically perfect evilginx2 proxy
behind an implausible story converts nobody and burns the engagement.
Design the story first, from real OSINT, then pick the smallest target
set that proves the objective.
## Inputs
- `plan/roe.json`: permitted pretext classes, out-of-scope users,
VIP exclusions, `data_handling`.
- OSINT handoff (from the OsintOperator): employee list, org chart,
email format, tech stack, current events (mergers, migrations).
