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.
npx skills add fatihkan/badi --skill pentest-socialgit clone --depth 1 https://github.com/fatihkan/badiWrote 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.
[](https://agentmods.dev/skills/fatihkan/badi/pentest-social)<a href="https://agentmods.dev/skills/fatihkan/badi/pentest-social"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-social/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.
<a href="https://agentmods.dev/skills/fatihkan/badi/pentest-social"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/pentest-social.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 13 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.01187 |
| Opus 5 | $0.00032 | $0.00593 |
| Sonnet 5 | $0.00013 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
pentest-social 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pentest-social
Social engineering strategy and awareness training advisory. NO live phishing campaign operation — this skill only does scenario design, target-list scoping, and debrief planning.
Triggers
- "phishing scenario"
- "social engineering plan"
- "pretext idea"
- "vishing scenario"
- "awareness training"
- "gophish setup for a phish simulation"
Engagement Discipline Boundaries
- Proof of authorization required — written client permission, an in-scope user list
- HR + Legal approval — employee targeting is coordinated with HR + Legal
- Employee psychological impact — misuse ends the engagement
- Plan a debrief — post-engagement training material for every target
- Targeting third parties — forbidden (the client provides them)
Phishing Scenario Types
| 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 |
Pretext Design (Authorized Engagement)
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
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.
- 3d ago First seen · 142 lines · 63 tokens per session scan A 351ae7e36cf7
pentest-social is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 1,187 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-06.
Other skills, from other repositories
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.