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 defense-strategiesgit 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/defense-strategies)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/defense-strategies"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/defense-strategies/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/defense-strategies"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/defense-strategies.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.00066 | $0.02135 |
| Opus 5.5 | $0.00026 | $0.00854 |
| Sonnet 5.5 | $0.00013 | $0.00427 |
| Haiku 4.5 | $0.00007 | $0.00214 |
Grade A, and why
defense-strategies 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Defense Strategies
Technical and human defense controls for preventing, detecting, and responding to social engineering attacks across all channels.
Knowledge Base
Defense-in-Depth Model for Social Engineering
Social engineering defense requires layered controls because no single control stops all attacks. The layers work together:
Layer 1: Perimeter (prevent delivery)
Email filtering, URL filtering, phone call screening
Layer 2: Technical enforcement (prevent exploitation)
MFA, conditional access, email authentication (DMARC)
Layer 3: Human detection (recognize attacks)
Awareness training, verification procedures, reporting culture
Layer 4: Process controls (prevent impact)
Dual authorization for financial transfers, callback verification
Layer 5: Response (minimize damage)
Incident response, account lockout, forensic analysis
Technical Controls
Email Authentication (prevent domain spoofing)
| Control | Purpose | Implementation |
|---|---|---|
| SPF | Authorize sending servers | DNS TXT record listing authorized IPs |
| DKIM | Cryptographic email signing | Public key in DNS, signing by mail server |
| DMARC | Policy enforcement for SPF/DKIM failures | DNS TXT record with policy (none/quarantine/reject) |
DMARC progression:
p=none-- Monitor mode, collect reportsp=quarantine-- Send failures to spamp=reject-- Block failures entirely
# Strong DMARC record
_dmarc.example.com. TXT "v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100"
DMARC limitations: Does not prevent display name spoofing, lookalike domains, or compromised legitimate accounts.
Email filtering and security:
- Anti-phishing engines (ML-based content analysis, URL reputation, sender reputation)
- URL rewriting and time-of-click analysis (URLs scanned when clicked, not just on delivery)
- Attachment sandboxing (detonation in isolated environment before delivery)
- Impersonation protection (flagging emails that spoof internal display names)
- External email tagging (
[EXTERNAL]banner on emails from outside the organization) - QR code scanning in attachments (defense against quishing)
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 · +66 tokens per session b49bbc183cdc
- 1mo ago First seen · 188 lines · 0 tokens per session scan A 892c6f732b14
defense-strategies is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 2,135 once invoked, about $0.0003 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.