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.
git 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/commands/hermeticormus/libresecops-claude-code/devsecops-setup)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/devsecops-setup"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/devsecops-setup/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/commands/hermeticormus/libresecops-claude-code/devsecops-setup"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/devsecops-setup.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.00034 | $0.00909 |
| Opus 5.5 | $0.00014 | $0.00364 |
| Sonnet 5.5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
devsecops-setup 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 21d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/devsecops-setup
Configure security scanning in an existing CI/CD pipeline, detecting the platform and adding appropriate security stages.
Trigger
Use when you need to add security scanning to an existing project's CI/CD pipeline, or when bootstrapping a new project with security-integrated CI/CD from day one. Appropriate for:
- Adding security to an existing pipeline that has none
- Auditing and improving an existing security pipeline
- Setting up CI/CD for a new project with security built in
- Migrating security scanning between CI/CD platforms
Input
The command operates on the current project directory. It detects:
- CI/CD platform: .github/workflows/*.yml (GitHub Actions), .gitlab-ci.yml (GitLab CI), Jenkinsfile (Jenkins), .circleci/config.yml (CircleCI)
- Project type: Language, framework, and package manager from manifest files
- Existing security scanning: What is already configured
- Optional flag:
--platform [github|gitlab|jenkins]-- force a specific platform - Optional flag:
--level [minimal|standard|comprehensive]-- security coverage level
Process
-
Platform Detection: Identify the CI/CD platform from configuration files in the repository. If multiple are present, ask which is primary.
-
Project Analysis: Determine the tech stack from package manifests, build files, and source code patterns. This informs which scanning tools are relevant.
-
Current State Audit: Parse existing pipeline configuration to identify:
- Which security scanning stages already exist
- How they are configured (thresholds, gates)
- What gaps remain
-
Gap Analysis: Compare current state against the selected coverage level:
- Minimal: Secret detection + SCA (known vulnerabilities)
- Standard: Minimal + SAST + container scanning (if applicable)
- Comprehensive: Standard + DAST + IaC scanning + SBOM generation + license compliance
-
Configuration Generation: Produce pipeline configuration for the missing stages:
- Use language-appropriate tools (e.g., Semgrep rules for the detected language, Bandit for Python-only)
- Configure caching for scan databases
- Set appropriate gates (block on critical/high for new projects, warn-only for existing projects with backlog)
- Add SARIF upload where the platform supports it
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.
- 21d ago Changed · +5 lines · +34 tokens per session c4c2d1b1a4a3
- 1mo ago First seen · 90 lines · 0 tokens per session scan A 84748321ad04
devsecops-setup is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 18d ago), licensed MIT. It adds 34 tokens to every session and 909 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
redteam
A read-only review of infrastructure settings, infrastructure-as-code, and CI/CD pipelines using MITRE ATT&CK attack paths. MITRE ATT&CK is a catalogue of techniques attackers use, while CI/CD means the automated process that builds, tests, and deploys software.
slsa
Check and improve SLSA compliance level.
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.
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.