القائمة
Social engineering pentest methodology — phishing strategy, pretexting, vishing scenario, awareness training advisory. No live phishing operation. Triggers on social engineering, phishing, vishing, pretext, awareness, OSINT-driven pretext, GoPhish, Evilginx, phishing simulation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | pentest-social |
| description | Social engineering pentest methodology — phishing strategy, pretexting, vishing scenario, awareness training advisory. No live phishing operation. Triggers on social engineering, phishing, vishing, pretext, awareness, OSINT-driven pretext, GoPhish, Evilginx, phishing simulation. |
| license | MIT |
| compatibility | Works with Claude Code |
| allowed-tools | Read Write Edit Grep |
| metadata | {"author":"badi","homepage":"https://github.com/fatihkan/badi-skills/tree/main/skills/pentest-social","badi-version":">=1.24.0","category":"pentest","scope":"advisory","inspired-by":"0xSteph/pentest-ai-agents social-engineer (advisory side)"} |
Social engineering strategy and awareness training advisory. NO live phishing campaign operation — this skill only does scenario design, target-list scoping, and debrief planning.
| Type | Example | Impact Measure |
|---|---|---|
| Mass phish | "Your password is expiring" (generic) | Awareness baseline |
| Spear phish | Personalized (role + name from LinkedIn) | Target role-specific test |
| Whaling | C-level target | High-risk target defense |
| Smishing | Over SMS | Mobile vector |
| Vishing | Phone (impersonate IT support) | Human verification procedure |
| Watering hole | Clone of a site the user visits often | Supply chain |
| QR phish | Physical QR sticker | Hybrid attack |
A good pretext = believable + urgency + hard to verify + typical action
Examples:
1. IT Support Pretext
- "Your Office365 account is locked, please verify via this link"
- Believable: common daily email
- Urgency: no account access
- Action: link click + cred input
2. Vendor Invoice Pretext
- "Payment for invoice number X is pending"
- Believable: finance/procurement related
- Urgency: due date passed
- Action: open the attachment (XLSX macro)
3. Internal HR Pretext
- "New performance review system - please log in"
- Believable: internal process
- Hard to verify: HR system change
- Action: cred input
# config.yml example
admin_server:
listen_url: 127.0.0.1:3333
use_tls: true
phish_server:
listen_url: 0.0.0.0:80
use_tls: false
Setup steps (the user runs manually):
This skill does not run any GoPhish command. Only the setup checklist + scenario writing.
## Vishing Scenario — "IT Helpdesk MFA Reset"
### Preparation
- OSINT: IT team names from LinkedIn
- Social media: organization structure
- Burner phone number + spoofing legal framework (within an authorized pentest)
### Scenario
- "Hi [target name], this is [IT team member name]. There's an issue with our MFA system,
could you read me your confirmation code so I can reset your account?"
- Prepare for pushback questions:
- "Where did you get my number" -> "Helpdesk inventory"
- "Will the director approve" -> "It's urgent, so I skipped that"
### Line
- Keep the conversation under 90 seconds
- Urgency through halting phrasing
- Not asking for creds, asking for the MFA code (push-approval bypass)
After the engagement ends:
Market and demand research procedures. Niche discovery, demand sizing, competitor/gap analysis, opportunity scoring, and pricing/positioning signals BEFORE building. Triggers on: market research, demand, niche, opportunity sizing, competitor analysis, TAM, positioning, pricing, go-to-market, validate idea, is there demand.
Choosing between app.json vs app.config.ts vs app.config.js, environment variables, variants, extra fields, plugin chain, and slug/scheme/bundle/version discipline. Triggers on app.json, app.config.ts, app.config.js, expo config, environment variable, .env, eas secret, variant, extra field, slug, scheme, bundle identifier, package name, version, build number, version code.
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin, plugin test, app.config plugin.
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.
iOS and Android build profiles with EAS Build, credentials management, build cache, secrets, and monorepo support. Triggers on eas build, eas.json, build profile, credentials, provisioning profile, keystore, push certificate, service account, build cache, eas secret, monorepo, development build, preview build, production build.
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production submit, release management.