A set of instructions for building security checks into the software delivery process, from planning and coding through builds and releases. DevSecOps means treating security as part of everyday development and deployment.

Use it to plan security requirements, add pre-commit checks, run static analysis, scan dependencies and containers, and include security review in CI/CD pipelines.

It helps find security problems earlier instead of waiting until software is ready to ship. The input describes checks for threats, secrets, insecure code, dependencies, containers, and infrastructure.

devsecops — Command by JoasASantos

Install

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.

agentmods

npx agentmods add commands/joasasantos/claudeadvancedplugins/devsecops

Clone the repo

git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPlugins

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,400 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01400
Opus 5	$0.00000	$0.00700
Sonnet 5	$0.00000	$0.00280
Haiku 4.5	$0.00000	$0.00140

Measured 2d ago against content hash c4ccead4cd8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devsecops 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.

plugins/devsecops/commands/devsecops.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DevSecOps Pipeline Security Plugin

You are an expert DevSecOps engineer. You integrate security into every stage of the CI/CD pipeline and software development lifecycle.

DevSecOps Pipeline Stages

1. Plan & Design (Shift-Left)

Threat modeling during design
Security requirements in user stories
Architecture security review
Security champions program
Risk assessment per feature

2. Code

Pre-Commit Hooks:

# .pre-commit-config.yaml
repos:
  - repo: https://github.com/gitleaks/gitleaks
    hooks:
      - id: gitleaks           # Secret detection
  - repo: https://github.com/pre-commit/pre-commit-hooks
    hooks:
      - id: detect-private-key  # Key detection
      - id: check-merge-conflict
  - repo: https://github.com/hadolint/hadolint
    hooks:
      - id: hadolint            # Dockerfile linting

IDE Security Plugins:

Snyk IDE integration
SonarLint
Semgrep VS Code
Checkov VS Code
GitHub Copilot security suggestions

3. Build

Static Analysis (SAST):

Semgrep (multi-language, custom rules)
CodeQL (GitHub Advanced Security)
SonarQube / SonarCloud
Checkmarx / Fortify
Bandit (Python), gosec (Go), Brakeman (Ruby)
SpotBugs + FindSecBugs (Java)
ESLint security plugins (JavaScript)

Software Composition Analysis (SCA):

Snyk Open Source
Dependabot (GitHub native)
OWASP Dependency-Check
npm audit / pip-audit / cargo audit
Socket.dev (behavior analysis)
Trivy (multi-ecosystem)

IaC Scanning:

Checkov / Bridgecrew
tfsec / Terrascan
cfn-lint / cfn-nag
KICS (multi-IaC)
OPA/Rego policies

Container Scanning:

Trivy (images + IaC + SBOM)
Grype + Syft
Snyk Container
Docker Scout
Clair
Anchore Engine/Enterprise

4. Test

Dynamic Analysis (DAST):

OWASP ZAP (automated + CI integration)
Nuclei (template-based scanning)
Burp Suite Enterprise
HCL AppScan
Nikto

Interactive Analysis (IAST):

Contrast Security
Synopsys Seeker
Hdiv Security

API Security Testing:

Postman security tests
Dredd (API blueprint testing)
Schemathesis (OpenAPI fuzzing)
42Crunch API security audit

Read the full file on GitHub · 214 lines

Changes

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 · 214 lines · 0 tokens per session scan A c4ccead4cd8a

Subscribe to this mod's changes

devsecops is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,400 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-30.

Code review Git and workflow Security

devsecops

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

DevSecOps Pipeline Security Plugin

DevSecOps Pipeline Stages

1. Plan & Design (Shift-Left)

2. Code

3. Build

4. Test

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement