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 HermeticOrmus/LibreSecOps-Claude-Code --skill social-engineering-taxonomygit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/social-engineering-taxonomy)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/social-engineering-taxonomy"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/social-engineering-taxonomy/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/hermeticormus/libresecops-claude-code/social-engineering-taxonomy"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/social-engineering-taxonomy.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.01764 |
| Opus 5.5 | $0.00019 | $0.00706 |
| Sonnet 5.5 | $0.00009 | $0.00353 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
social-engineering-taxonomy 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 12d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Engineering Taxonomy
Classification of social engineering attack types, psychological principles exploited, recognition patterns, and organizational defense strategies.
Knowledge Base
Definition
Social engineering is the psychological manipulation of people into performing actions or divulging information that benefits the attacker. Unlike technical attacks that exploit software vulnerabilities, social engineering exploits human cognitive biases, trust relationships, and organizational processes.
Attack Type Classification
Email-Based Attacks
| Type | Description | Targeting | Sophistication |
|---|---|---|---|
| Mass phishing | Untargeted emails to many recipients | None - spray and pray | Low |
| Spear phishing | Targeted emails using personal information | Specific individuals | Medium-High |
| Whaling | Phishing targeting executives/senior leadership | C-suite, board members | High |
| BEC (Business Email Compromise) | Impersonating executives to request actions | Finance, accounting, HR | High |
| Vendor impersonation | Impersonating suppliers requesting payment changes | Accounts payable | High |
| Lateral phishing | Phishing from a compromised internal account | Internal targets | Very High |
Voice-Based Attacks (Vishing)
| Type | Description | Common Pretext |
|---|---|---|
| IT support scam | Impersonating IT helpdesk | "We detected a problem with your account" |
| Authority impersonation | Pretending to be law enforcement or government | "This is regarding a tax investigation" |
| Vendor callback | Requesting callback to attacker-controlled number | "Call us back to verify your account" |
| Deepfake voice | AI-generated voice mimicking known individuals | CFO requesting urgent wire transfer |
SMS/Messaging (Smishing)
| Type | Description | Common Pretext |
|---|---|---|
| Package delivery | Fake shipping notifications | "Your package could not be delivered" |
| Banking alerts | Fake fraud alerts from banks | "Suspicious activity on your account" |
| MFA code theft | Requesting MFA codes | "Enter the code we just sent you" |
| Job offer scams | Fake recruiting messages | "We have a position matching your profile" |
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.
- 12d ago Changed · +5 lines · +47 tokens per session 88282121f5c5
- 1mo ago First seen · 143 lines · 0 tokens per session scan A 8623305056fd
social-engineering-taxonomy is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 47 tokens to every session and 1,764 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.