devsecops-expert

A rule set for arranging security checks in a CI/CD pipeline, the automated process that builds and tests software. It specifies when to scan for secrets, code flaws, infrastructure mistakes, and vulnerable build outputs.

In plain words
What is it for?
Use it when creating or reviewing GitHub Actions or GitLab pipelines that must scan before downloading dependencies, run tests, check final containers, sign artifacts, and use short-lived cloud access.
Why use it?
It helps prevent unsafe code or exposed credentials from reaching later build or release steps, while requiring failed checks to stop the pipeline.

Skill for Claude CodeCodex

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 skills/chama-x/groundrules/devsecops-expert
Any agent
npx skills add chama-x/GroundRules --skill devsecops-expert
Clone the repo
git clone --depth 1 https://github.com/chama-x/GroundRules

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 292 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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00292
Opus 5 $0.00012 $0.00146
Sonnet 5 $0.00005 $0.00058
Haiku 4.5 $0.00002 $0.00029

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

Security

Grade A, and why

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

.agents/skills/devsecops-expert/SKILL.md · 21 lines

What it actually says

DevSecOps Pipeline Configuration

This is a configuration profile, not a textbook. You already know how CI/CD tools work. When generating or auditing pipelines, enforce this exact structural sequence:

Mandatory Pipeline Sequence

  1. Pre-Flight / Secret Scan: (Trivy, TruffleHog, or Gitleaks). Must block the pipeline BEFORE any dependencies are downloaded or code is built.
  2. Static Analysis & Linting: (Checkov, tfsec for IaC; Semgrep or equivalent for code).
  3. Build & Unit Tests.
  4. Artifact / Container Scanning: (Trivy). Scan the final built image, not just the source.
  5. Provenance: Generate SLSA provenance and use Sigstore/Cosign for artifact signing.

Hard Constraints

  • Fail-Fast: Any High or Critical vulnerability must exit with code > 0 and fail the pipeline immediately.
  • Least Privilege: CI/CD runners must use OIDC (OpenID Connect) to authenticate to cloud providers (AWS, GCP, Azure). Long-lived static credentials are forbidden.
  • Pinned Actions: GitHub Actions or GitLab includes MUST be pinned to a specific commit SHA, not @v2 or @main.
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.

  1. 2d ago First seen · 21 lines · 24 tokens per session scan A 0c00fdec7ff9

Subscribe to this mod's changes

devsecops-expert is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 18d ago), licensed MIT. It adds 24 tokens to every session and 292 once invoked, about $0.0001 per session on Opus 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.