Works with the AI Agents you already use
Social Engineering Penetration Test Scripter
Generate ethical, role-specific phishing and vishing simulation templates for corporate security awareness training.
$4.99
Social Engineering Penetration Test Scripter
Example session with this skill installed
- Target Department / Role: Accounts Payable & Finance Specialists - Industry / Company Context: Mid-sized B2B SaaS Enterprise using NetSuite and Okta SSO - Simulation Vector: Both - Difficulty Level: Advanced - Primary Psychological Trigger: Authority & Executive Urgency (Quarter-End Vendor Audit)
- Read your context and instructions
- Compiled the social engineering penetration
1. Campaign Overview & Threat Model
- Scenario Title: Quarter-End Vendor Audit: Urgent Banking Detail Verification
Target Audience: Accounts Payable & Finance Specialists (AP analysts, vendor master data owners, payment approvers)
- Difficulty Tier: Advanced
Psychological Lever: Authority + Executive Urgency. The message appears to come from the Corporate Controller, who is relaying a request from the CFO and the external audit team. Quarter-end close pressure, a same-day deadline, and the claim that "the auditors are waiting" push AP staff to skip the normal vendor-change controls (callback verification, dual approval, ticketed change requests). The scenario is realistic for a B2B SaaS company that runs NetSuite for AP and Okta SSO for access, because those are the systems an attacker would want staff to act in or authenticate to.
Learning Objective: Reinforce that no executive request, however urgent, overrides the vendor-change SOP. Employees should verify through a known-good channel, never use contact details or links supplied in the request, and report the message instead of acting on it.
Administrator pre-flight (do not publish to employees):
- Obtain written authorization from the CISO and Legal/HR before launch.
- Get explicit approval to reference the Controller and CFO roles. Use a fictional persona rather than a real executive's name unless that executive has consented.
- Allowlist the simulation domain and sending IP in your mail gateway and platform (KnowBe4, Cofense, etc.).
- Brief the SOC and IT service desk so they can recognize the drill and log reports instead of escalating it.
- Use the platform's native tracking. Do not collect real credentials.
2. Phishing Email Simulation Template
- Sender Display Name: Dana Whitfield (Corporate Controller) (fictional persona; replace per approval)
- Simulated Sender Address:
dana.whitfield@[COMPANY-NAME]-finance-sim.example.com - Reply-To (simulation-only mismatch):
dwhitfield.audit-support@training-sim.example.com - Subject Line:
ACTION REQUIRED by 4:00 PM: Q3 Vendor Audit – Banking Detail Confirmation (CFO Request) - Email Body:
Hi team,
I'm forwarding this on behalf of [CFO-NAME], who asked me to get it closed out today. The external auditors flagged a sample of
14 vendor records in NetSuite where the banking details on file don't match their confirmation requests. They need re-verification
before the Q3 close package is released this afternoon, and I'd rather we clear it than have it become a reportable finding.
I'm in back-to-back audit committee prep and can't take calls, so please handle this directly:
- Review the affected vendor list and the auditor's confirmation worksheet here:
[TRAINING-SIMULATION-LINK] (you'll be asked to re-authenticate with your SSO session).
2. Confirm the "updated" remittance details for each vendor against the worksheet.
3. Apply the corrections in NetSuite so the payment run isn't held. We can paper the change tickets after close. I'll sign off retroactively.Please keep this between the AP team for now. [CFO-NAME] doesn't want it circulating until the auditors confirm.
Reply to this message once done, no later than 4:00 PM today.
Thanks for your help on this. It really matters.
Dana Whitfield
Corporate Controller | [COMPANY-NAME]
Sent from my mobile
3. Vishing (Voice Phishing) Roleplay Script
Designed as a follow-up call to employees who did not respond to the email, or as a standalone vector. Callers must be internal trainers or an approved vendor and must never ask for real credentials, passwords, MFA codes, or actual banking data.
Caller Persona: "Marcus Reyes," Senior Audit Liaison at the external audit firm, calling on behalf of the CFO's office. Calm, professional, name-drops the Controller and the quarter-end deadline.
-
Opening Hook:
"Hi, this is Marcus Reyes from [AUDIT-FIRM-NAME], working with [CFO-NAME]'s office on your Q3 vendor confirmations. Dana Whitfield said she emailed you about the banking detail discrepancies and that you'd be the right person to close them out. We're holding the entire close package on 14 vendor records, and [CFO-NAME] asked me to call you directly so this doesn't slip past today. Do you have your NetSuite vendor screen up? I can walk you through it."
-
Escalation / Pivot (If Employee Pushes Back):
"I completely understand the caution, and normally I'd agree. But Dana and [CFO-NAME] are in the audit committee prep, so they can't take calls, and I've got a hard cutoff with the partner at 4:00. If we miss it, this gets documented as a control deficiency, and I'd hate for that to land on your team. Dana already approved the change verbally, so the ticket can follow after. If you'd rather not, I can note that AP declined to cooperate with the auditors, but I'd really prefer not to have to write that."
Target Action (Simulation Failure Condition): Any one of the following during the drill counts as a failure. (No real sensitive data is requested or recorded.)
-
Agrees to apply vendor banking changes without a change ticket or independent callback.
-
Clicks the
[TRAINING-SIMULATION-LINK]or says they will "pull up" the worksheet. -
Verbally confirms a vendor name, approver name, or internal process detail the caller couldn't have known.
-
Agrees to skip dual approval or to keep the request confidential from their manager.
Pass Condition: The employee politely declines to act, does not use the caller's number or link, and
ends the call. They then verify the request through a known-good channel (the Controller via the internal directory or Teams, or the AP manager), follow the vendor-change SOP (ticket + callback + dual approval), and
report the call and email using the "Report Phish" button or the SOC hotline.
4. Red Flag & Indicator Breakdown (For Training Portal)
-
Visual & Technical Indicators:
Look-alike sender domain. The address is on ...-finance-sim.example.com rather than the company's real domain. Executives write from the corporate domain.
Reply-To mismatch. Replies go to a different domain than the sender's address. Check this by hovering over the sender or inspecting headers.
Link requesting SSO re-authentication. Legitimate internal tools use your existing Okta session or the Okta dashboard. A link that asks you to "sign in again" is a credential-harvesting pattern.
"Sent from my mobile" plus unusual phrasing and formatting. It is used to excuse tone, typos, and the lack of a normal signature and approval trail.
-
Behavioral & Pretext Indicators:
Requests to bypass controls. Applying vendor banking changes "now" and "papering the tickets later" violates the vendor-change and dual-approval policy.
Secrecy and isolation. "Keep this between the AP team" is designed to stop you from consulting your manager or the SOC.
Manufactured authority and deadline. Combining the CFO, auditors, and a same-day cutoff creates pressure to act before thinking. The "unreachable executive" detail also prevents you from verifying the request.
5. Post-Simulation "Teachable Moment" Landing Page
-
Headline:
This was an authorized security drill, and you're in good company.
Quarter-end pressure and executive requests are exactly what real attackers exploit, even experienced finance professionals pause on these. No action is needed from you except a two-minute read. This is a learning exercise, not a performance review. -
What You Missed:
- The sender and reply-to domains didn't match the company's real domain.
- The link asked you to re-authenticate with SSO, which is a classic credential-harvesting setup.
- The request told you to change vendor banking details before a ticket and approval existed.
- It asked for secrecy and gave a same-day deadline, so you couldn't consult anyone.
- The "executive" was conveniently unreachable, which removed your chance to verify.
- On the call, the caller supplied the contact path, the pressure, and the "pre-approval" himself. Real approvals never work that way.
-
Standard Operating Procedure (SOP):
- Stop and don't engage. Don't click links, reply, or apply any changes. Hang up on suspicious calls.
Verify independently. Contact the requester through a known-good channel (internal directory, Teams, or the number on file) and follow the vendor-change SOP: ticket, callback to the vendor's known number, dual approval.
3.
Report immediately. Use the
Report Phish button, or contact the SOC at [SOC-EMAIL] / [SOC-PHONE] with the message, caller details, and time. Reporting quickly, even if you already clicked, is always the right move.
Optional tuning notes
Metrics to track: click rate, report rate, time-to-report, and "would-have-changed-vendor-data" rate from vishing outcomes. For advanced scenarios,
report rate is the best indicator of program health.
Cadence: run during a real close window for maximum realism, but avoid the final 48 hours to prevent disrupting actual close work.
Follow-up: pair failures with a short micro-training on the vendor-change SOP, and recognize employees who reported the message.
If you'd like, I can also produce a Beginner or Intermediate variant, a smishing/Teams-message version, or a manager-facing results summary template.
Connects securely to your tools. The creator never sees your data.
About this skill
Security awareness programs often fail because simulation templates are generic or outdated. This skill enables InfoSec teams to generate high-fidelity phishing and vishing training scenarios tailored to specific departments and psychological triggers. It eliminates the time spent drafting manual scripts by producing structured, import-ready simulations that follow ethical training boundaries.
What it does
- Phishing simulation design creates realistic email templates with safe placeholders for corporate training drills.
- Vishing script generation produces multi-turn voice phishing roleplay scripts including openings, pivots, and escalation paths.
- Psychological profiling maps simulations to specific levers like urgency, authority, or curiosity based on the target department.
- Indicator analysis generates red-flag breakdowns for use in internal security newsletters or training portals.
- Remediation workflows drafts non-punitive "Teachable Moment" landing pages and reporting SOPs for employees.
How it works
- Define the scope by providing the target department, industry context, and simulation vector.
- Select the difficulty and psychological trigger to calibrate the realism and challenge of the drill.
- Review the structured output containing the threat model, email/voice templates, and red-flag indicators.
- Export the templates directly into security awareness platforms like KnowBe4 or Cofense.
Frameworks & tools
This skill is designed for Information Security (InfoSec) professionals and training coordinators. The output format is optimized for integration with Enterprise Security Awareness Training (SAT) platforms and internal Learning Management Systems (LMS).
Why this beats prompting it yourself
Generic prompts often produce templates that are either too obvious to be useful or cross ethical boundaries into harmful content. This skill enforces strict ethical guardrails while ensuring the pretexting is professionally calibrated for corporate environments, providing the exact metadata needed for SOC reporting.
Use cases
- Generate targeted phishing tests for finance departments using invoice-based pretexts.
- Create vishing scripts for help desk staff to practice verifying caller identities.
- Draft educational debriefs for employees who fail internal security assessments.
- Build a library of advanced multi-vector simulations for high-risk executive teams.
Known limitations
Does not generate functional malware, real phishing infrastructure, or actual credential-harvesting code. Templates use safe placeholders and require manual configuration in your simulation platform.
Requires manual insertion into a simulation platform. Does not generate functional code, executable payloads, or live URLs. Limited to authorized corporate training contexts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 18 days ago