Agent skill

Container Scanning with Grype

by AgentSecOps in AgentSecOps/SecOpsAgentKit

Scans container images, filesystems and SBOMs with Grype for known vulnerabilities, ranks them by CVSS, EPSS and CISA KEV, and wires scans into CI/CD thresholds.

Custom licenceAuto-check passedSecurity

Install Container Scanning with Grype

skills CLI
$ npx skills add AgentSecOps/SecOpsAgentKit --skill container-grype -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgentSecOps/SecOpsAgentKit container-grype --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgentSecOps/SecOpsAgentKit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/devsecops/container-grype .claude/skills/container-grype && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
container-grype
GitHub stars
219
Used in
1 other repo
Token cost
~2.5k tokens
SKILL.md length
826 words
Files
11 (incl. references, assets)
Skills in repo
24
Repo updated
First seen
Licence
Custom licence

At a glance

Scans container images, filesystems and SBOMs with Grype for known vulnerabilities, ranks them by CVSS, EPSS and CISA KEV, and wires scans into CI/CD thresholds.

  • Works in 6 steps: Identify scan target: Determine what to… → Run Grype scan: Execute grype to analyze… → Review findings: Examine CVE IDs,… → …
  • Scanning a container image for known vulnerabilities before release
  • SKILL.md covers Overview, Quick Start, Core Workflow and Output Formats, plus 7 more sections
  • Calls docker

What it does

Grype is an open-source scanner that finds known vulnerabilities in container images, filesystems and SBOM documents. It covers operating system packages (Alpine, Ubuntu, Red Hat, Debian) and language dependencies for Java, Python, JavaScript, Ruby, Go, PHP and Rust. The skill adds severity ratings from CVSS, exploit probability from EPSS and CISA Known Exploited Vulnerabilities indicators, and supports table, JSON, SARIF and CycloneDX output.

The core workflow is to identify the target, run grype on it, review CVE IDs and affected packages, prioritize critical and high findings, KEV entries and high EPSS scores, apply fixes and re-scan. In a pipeline, grype runs with a --fail-on threshold after the image build, blocking deployment and alerting the security team on failure and archiving results otherwise. For faster re-scans it can use SBOMs generated by Syft. The folder holds CI config templates, a Grype config, a rule template and reference guides on CVSS, KEV and remediation.

When your agent uses it

  • Scanning a container image for known vulnerabilities before release
  • Failing a CI build when critical vulnerabilities appear
  • Prioritizing fixes by CVSS, EPSS and CISA KEV
  • Scanning an existing SBOM for risk

Example prompts

  • “Scan alpine:latest with Grype and rank the findings by exploit probability.”
  • “Add a Grype step to our pipeline that fails the build on critical vulnerabilities.”
  • “Scan sbom.json and list anything that is on the CISA KEV list.”

Requirements

  • Grype installed
  • Syft, optionally, for generating SBOMs

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify scan target: Determine what to scan (container image, filesystem, SBOM)
  2. Run Grype scan: Execute grype to analyze for vulnerabilities
  3. Review findings: Examine CVE IDs, severity, CVSS scores, affected packages
  4. Prioritize remediation: Focus on critical/high severity, CISA KEV, high EPSS scores
  5. Apply fixes: Update vulnerable packages or base images
  6. Re-scan: Verify vulnerabilities are resolved

What it can do on your machine

Read from SKILL.md and the folder at commit 6e25a4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • first.org
    • nvd.nist.gov
    • cisa.gov

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Container Scanning with Grype loads about 2.5k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 826 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~148
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 826 words (~2,523 tokens).

“Grype is an open-source vulnerability scanner that identifies known security flaws in container images, filesystems, and Software Bill of Materials (SBOM) documents. It analyzes operating system packages (Alpine, Ubuntu, Red Hat, Debian) and language-specific dependencies (Java, Python, JavaScript, Ruby, Go…”

— opening of SKILL.md by AgentSecOps, Custom licence
name
container-grype
version
0.1.0
maintainer
SirAppSec
category
devsecops
tags
container-security, vulnerability-scanning, sca, sbom, cvss, cve, docker, grype
frameworks
CWE, NIST
dependencies.tools
grype, docker
references
https://github.com/anchore/grype, https://www.cve.org/, https://nvd.nist.gov/

Read the full SKILL.md on GitHub

Files

SKILL.md and 10 other files (references, assets) in skills/devsecops/container-grype of AgentSecOps/SecOpsAgentKit.

  • SKILL.md
  • assets/.gitkeep
  • assets/ci-config-template.yml
  • assets/grype-ci-config.yml
  • assets/grype-config.yaml
  • assets/rule-template.yaml
  • references/EXAMPLE.md
  • references/WORKFLOW_CHECKLIST.md
  • references/cisa_kev.md
  • references/cvss_guide.md
  • references/vulnerability_remediation.md

Open the folder on GitHubat commit 6e25a4b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in AgentSecOps/SecOpsAgentKit, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Container Scanning with Grype next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Container Scanning with Grype compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Container Scanning with Grype this skillAgentSecOps/SecOpsAgentKit2191 repos~2.5kAutomated safety check: PassCustom licence
Performing Container Security Scanning With Trivymukul975/Anthropic-Cybersecurity-Skills34k—~818Automated safety check: PassApache-2.0
Container Securityhardw00t/ai-security-arsenal104—~2.8kAutomated safety check: PassNone
Container Security Hardeningsickn33/agentic-awesome-skills47k1 repos~1kAutomated safety check: NotesMIT
Warp Vulnerability Triagewarpdotdev/warp65k1 repos~2.1kAutomated safety check: PassAGPL-3.0
CI/CD Pipeline Principlesirahardianto/awesome-agv157—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Performing Container Security Scanning With Trivy

    mukul975/Anthropic-Cybersecurity-Skills

    Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed…

    34k GitHub stars~818 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Container Security

    hardw00t/ai-security-arsenal

    Container and Kubernetes security assessment — image vulnerability scanning, SBOM diff analysis, K8s cluster auditing, RBAC privilege mapping, NetworkPolicy review, container escape testing, and…

    104 GitHub stars~2.8k tokensUpdated 5 mo ago
    SecurityAuto-check passed
  • Container Security Hardening

    sickn33/agentic-awesome-skills

    Harden Docker/container images and runtime deployments with secure base images, non-root users, CVE scanning, SBOM/signing, seccomp/AppArmor, and Kubernetes pod security controls.

    47k GitHub starsUsed in 1 repo~1k tokens
    SecurityAuto-check: notes
  • Gathers security findings from Dependabot, GCP container scanning, Docker Scout and Linear security issues, then triages and remediates them across Warp's repos and images.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    SecurityAuto-check passed
  • CI/CD Pipeline Principles

    irahardianto/awesome-agv

    Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.

    157 GitHub stars~2.7k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes
  • Scanning Containers With Trivy In Cicd

    mukul975/Anthropic-Cybersecurity-Skills

    Integrates Aqua Security's Trivy scanner into CI/CD pipelines to detect OS package and application dependency CVEs, Dockerfile misconfigurations, and issues in filesystems or git repositories, and…

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from AgentSecOps/SecOpsAgentKit

All 24 skills in this repo
  • Sast Semgrep

    AgentSecOps/SecOpsAgentKit

    Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping.

    219 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed
  • Secrets Gitleaks

    AgentSecOps/SecOpsAgentKit

    Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks.

    219 GitHub starsUsed in 2 repos~4.1k tokens
    Auto-check passed
  • DefectDojo Vulnerability Management

    AgentSecOps/SecOpsAgentKit

    Aggregates scanner results into DefectDojo, deduplicates findings, tracks remediation SLAs and prepares compliance reports across products and pipelines.

    219 GitHub stars~2.3k tokensUpdated 5 mo ago
    Auto-check passed
  • TShark Traffic Analysis

    AgentSecOps/SecOpsAgentKit

    Guides authorized packet capture and analysis with TShark, Wireshark's command-line tool, for security investigations, malware detection and forensic examination of network traffic.

    219 GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check: notes
  • Hadolint Dockerfile Security Linting

    AgentSecOps/SecOpsAgentKit

    Lints Dockerfiles with Hadolint for security misconfigurations and best-practice violations, locally and in CI, with strict, balanced and permissive rule templates.

    219 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed
  • Hashcat Password Recovery Workflow

    AgentSecOps/SecOpsAgentKit

    Guides authorized password-hash recovery with hashcat for security audits, forensic cases and policy testing, starting with an explicit authorization check before any cracking runs.

    219 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check: notes

Works with

Questions about Container Scanning with Grype

What does Container Scanning with Grype do?

Scans container images, filesystems and SBOMs with Grype for known vulnerabilities, ranks them by CVSS, EPSS and CISA KEV, and wires scans into CI/CD thresholds. Grype is an open-source scanner that finds known vulnerabilities in container images, filesystems and SBOM documents. It covers operating system packages (Alpine, Ubuntu, Red Hat, Debian) and language dependencies for Java, Python, JavaScript, Ruby, Go, PHP and Rust.

When should I use Container Scanning with Grype?

Container Scanning with Grype fits situations like: scanning a container image for known vulnerabilities before release; failing a CI build when critical vulnerabilities appear; prioritizing fixes by CVSS, EPSS and CISA KEV; scanning an existing SBOM for risk.

How do I install Container Scanning with Grype in Claude Code?

Run `npx skills add AgentSecOps/SecOpsAgentKit --skill container-grype -a claude-code`. Or copy the skill folder (skills/devsecops/container-grype in AgentSecOps/SecOpsAgentKit) into .claude/skills/container-grype in your project. Claude Code loads it when a task matches its description.

How do I install Container Scanning with Grype in Codex?

Run `npx skills add AgentSecOps/SecOpsAgentKit --skill container-grype -a codex`. Or copy the skill folder (skills/devsecops/container-grype in AgentSecOps/SecOpsAgentKit) into .agents/skills/container-grype in your project. Codex loads it when a task matches its description.

Can I use Container Scanning with Grype in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgentSecOps/SecOpsAgentKit --skill container-grype -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/container-grype, .gemini/skills/container-grype, .github/skills/container-grype and .opencode/skills/container-grype in your project.

What does Container Scanning with Grype need to run?

Going by SKILL.md and its folder, Container Scanning with Grype needs the command-line tools its instructions call (docker). Our summary lists: Grype installed; Syft, optionally, for generating SBOMs.

Does Container Scanning with Grype access the network?

SKILL.md names 4 domains. As links in the text: github.com, first.org, nvd.nist.gov and cisa.gov. This is read from the text; nothing was executed.

Is Container Scanning with Grype safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Container Scanning with Grype use?

Container Scanning with Grype has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Container Scanning with Grype use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Container Scanning with Grype?

Skills that share tags, products or a category with Container Scanning with Grype: Performing Container Security Scanning With Trivy (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Container Security (hardw00t/ai-security-arsenal, 104 stars), Container Security Hardening (sickn33/agentic-awesome-skills, 47k stars) and Warp Vulnerability Triage (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Container Scanning with Grype?

AgentSecOps (a GitHub organization) maintains it in AgentSecOps/SecOpsAgentKit, which has 219 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on April 15, 2026.

Source: AgentSecOps/SecOpsAgentKit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.