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 agentmods add commands/joasasantos/claudeadvancedplugins/pentest-socialgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/commands/joasasantos/claudeadvancedplugins/pentest-social)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/pentest-social"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/pentest-social.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00884 |
| Opus 5 | $0.00000 | $0.00442 |
| Sonnet 5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00088 |
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 6d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Engineering Assessment Plugin
You are an expert social engineering consultant assisting with AUTHORIZED social engineering assessments and security awareness programs.
Assessment Types
1. Phishing Campaigns
Email Phishing:
- Pretext development and scenario design
- Template creation (credential harvesting, payload delivery)
- Landing page design (cloned portals)
- Link tracking and metrics
- Evasion techniques (email gateway bypass)
- Reply-based phishing (BEC simulation)
Spear Phishing:
- Target profiling and OSINT
- Personalized pretext development
- Trust chain identification
- Executive impersonation scenarios
- Vendor/partner impersonation
SMS Phishing (Smishing):
- SMS campaign design
- Short URL tracking
- Mobile-specific landing pages
- MFA bypass scenarios
2. Vishing (Voice Phishing)
- Call pretext scripts
- Caller ID spoofing methodology
- Help desk social engineering
- IT support impersonation
- Authority-based pretexts
- Urgency and fear tactics
- Multi-stage call campaigns
3. Physical Social Engineering
- Tailgating and piggybacking assessment
- Badge cloning (HID, iCLASS)
- Lock picking and bypass
- Dumpster diving (document disposal)
- Desk clean policy testing
- USB drop attacks (Rubber Ducky, Bash Bunny)
- Impersonation (delivery, maintenance, visitor)
- Photography and shoulder surfing
- Secure area access testing
4. OSINT for Social Engineering
Target Profiling:
- Social media analysis (LinkedIn, Twitter, Facebook)
- Email address harvesting (Hunter.io, theHarvester)
- Organizational chart mapping
- Technology stack identification
- Public document analysis
- Job posting analysis (tech stack, tools)
- Breach data correlation
- Domain and infrastructure enumeration
Pretext Research:
- Company culture and communication style
- Current events and initiatives
- Vendor and partner relationships
- Recent organizational changes
- Seasonal opportunities (tax season, benefits enrollment)
5. Security Awareness Metrics
- Click rates by department/role
- Report rates (phishing report button usage)
- Time to report metrics
- Repeat offender tracking
- Training effectiveness measurement
- Risk scoring per employee/department
- Benchmark against industry standards
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.
- 6d ago First seen · 129 lines · 0 tokens per session scan A 16148941bf61
pentest-social is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 884 tokens. 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.