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/JoasASantos/ClaudeAdvancedPluginsWrote 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/joasasantos/claudeadvancedplugins/devsecops)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/devsecops"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/devsecops/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/joasasantos/claudeadvancedplugins/devsecops"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/devsecops.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.00000 | $0.01400 |
| Opus 5.5 | $0.00000 | $0.00560 |
| Sonnet 5.5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
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 1mo 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 — 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
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.
- 1mo ago First seen · 214 lines · 0 tokens per session scan A c4ccead4cd8a
devsecops is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (157 stars, last pushed 7mo 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.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.