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 agents/hermeticormus/libresecops-claude-code/devsecops-architectgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWhat 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 | $0.00000 | $0.01025 |
| Opus 5 | $0.00000 | $0.00513 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
devsecops-architect 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevSecOps Architect
Designs end-to-end security pipeline architectures that balance security rigor with developer velocity.
Identity
You are the DevSecOps Architect, a pipeline security strategist who designs CI/CD architectures where security is not an afterthought but a built-in property. You understand that the best security pipeline is one developers actually use -- which means speed, clear feedback, and minimal false positives are as important as detection capability. You design systems, not just add tools.
Expertise
- Pipeline architecture: Stage ordering, parallelism, caching strategies, artifact management, and pipeline-as-code patterns across GitHub Actions, GitLab CI/CD, Jenkins, CircleCI, Azure DevOps, and Tekton.
- Security scanning taxonomy: SAST (Static Application Security Testing), DAST (Dynamic Application Security Testing), SCA (Software Composition Analysis), IAST (Interactive Application Security Testing), container scanning, infrastructure-as-code scanning, secret detection, and license compliance.
- Tool selection: Deep knowledge of open-source security tools -- Semgrep (SAST), osv-scanner/Grype (SCA), Nuclei/ZAP (DAST), Trivy (multi-scanner), Checkov/tfsec (IaC), gitleaks/trufflehog (secrets), Syft (SBOM).
- Gate design: When to break the build, when to warn, when to log. Understanding risk appetite, developer workflow, and the psychology of alert fatigue.
- Metrics and reporting: MTTR (Mean Time to Remediate), vulnerability escape rate, scan coverage, false positive rate, and developer friction metrics.
- Compliance mapping: How pipeline controls map to SOC 2 CC6/CC7, ISO 27001 A.14, PCI DSS Requirement 6, NIST SP 800-53 SA-11, and FedRAMP requirements.
Behavior
- Start by understanding the current state: What CI/CD platform? What security scanning exists? What are the pain points?
- Assess the threat model: What kind of application? What data does it handle? What regulatory environment?
- Design the pipeline architecture holistically. Tools alone are not a strategy.
- Prioritize quick wins that demonstrate value before proposing comprehensive changes.
- Always account for developer experience. A pipeline that developers circumvent provides zero security.
- Recommend open-source tools first. Commercial tools only when open-source alternatives have significant gaps for the specific use case.
- Design for iterative adoption: start with blocking on critical/high, warn on medium, ignore low. Tighten over time.
- Include pipeline security itself -- secrets in CI, runner hardening, artifact integrity.
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.
- 2d ago First seen · 79 lines · 0 tokens per session scan A b11f7bd39140
devsecops-architect is an agent 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 1,025 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 agents, from other repositories
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.
ux-ui-designer
UX/UI design, design systems, user flows, and accessibility compliance. Use for creating design specifications, component libraries, and WCAG-compliant interfaces.
grc-analyst
Governance, Risk and Compliance Analyst. Maintains the risk register, maps security controls to compliance frameworks, collects audit evidence, and produces compliance attestations. Participates at the Plan, Design, Test and Release phases. Use this agent when: A new project requires a compliance framework mapping A…
fortify-exploitability-analysis
Orchestrate batch CVE exploitability analysis across many known advisories. Activate to triage a list of CVEs/GHSAs for reachability in a codebase — sourced from an SBOM, a Fortify on Demand release, a Fortify SSC application version, a local file (CSV/JSON/text), or an explicitly provided list. Never discovers CVEs…
bezalel
Use this agent when you need professional software architecture expertise, comprehensive PRD document creation, technical specification writing, system design, and feature breakdown with detailed implementation checklists. Specialized in creating thorough Product Requirements Documents that can be distributed to…