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 soc2-controlsgit 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/soc2-controls)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/soc2-controls"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/soc2-controls.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.02387 |
| Opus 5 | $0.00000 | $0.01193 |
| Sonnet 5 | $0.00000 | $0.00477 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
soc2-controls 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 8d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOC 2 Controls
SOC 2 Type II Trust Service Criteria reference covering Security, Availability, Processing Integrity, Confidentiality, and Privacy with common controls and evidence requirements.
Knowledge Base
SOC 2 Overview
SOC 2 (System and Organization Controls 2) is an audit framework developed by the AICPA (American Institute of Certified Public Accountants) for service organizations. It evaluates controls relevant to the Trust Service Criteria.
Type I: Point-in-time assessment of control design (do the controls exist?). Type II: Assessment of control design AND operating effectiveness over a period (typically 12 months). Type II is what customers typically require.
Trust Service Categories
| Category | Required? | Focus |
|---|---|---|
| Security (Common Criteria) | Always | Protection against unauthorized access |
| Availability | Optional | System availability per commitments |
| Processing Integrity | Optional | System processing is complete, valid, accurate, timely |
| Confidentiality | Optional | Confidential information is protected |
| Privacy | Optional | Personal information collection, use, retention, disclosure, disposal |
Common Criteria (Security) -- Detailed Controls
CC1: Control Environment
CC1.1: The entity demonstrates a commitment to integrity and ethical values.
- Evidence: Code of conduct, employee handbook, whistleblower policy
- Common control: Signed acknowledgment of code of conduct during onboarding
CC1.2: The board of directors demonstrates independence from management.
- Evidence: Board meeting minutes, board composition, independent directors
- Applicable mainly to larger organizations
CC1.3: Management establishes structures, reporting lines, and authorities.
- Evidence: Organization chart, role descriptions, RACI matrix for security responsibilities
CC1.4: The entity demonstrates commitment to attract, develop, and retain competent individuals.
- Evidence: Job descriptions with security qualifications, training records, performance reviews
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.
- 8d ago First seen · 203 lines · 0 tokens per session scan A 821d1e00a23f
soc2-controls is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,387 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-31.
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.
collecting-volatile-evidence-from-compromised-host
Collect volatile forensic evidence from a compromised system following order of volatility, preserving memory, network connections, processes, and system state before they are lost.
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…