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 skills add harness/harness-ai --skill configure-container-scangit clone --depth 1 https://github.com/harness/harness-aiWrote 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/skills/harness/harness-ai/configure-container-scan)<a href="https://agentmods.dev/skills/harness/harness-ai/configure-container-scan"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/configure-container-scan/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/skills/harness/harness-ai/configure-container-scan"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/configure-container-scan.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.00176 | $0.04157 |
| Opus 5 | $0.00088 | $0.02079 |
| Sonnet 5 | $0.00035 | $0.00831 |
| Haiku 4.5 | $0.00018 | $0.00416 |
Grade A, and why
configure-container-scan 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 10d 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.
This is a copy
100% identical to configure-container-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Container Scan
Add a container image scanning step to an existing Harness pipeline using the native HarnessSCA STO scanner.
Instructions
Step 1: Establish Scope and Pipeline Context
Ask for org, project, and pipeline identifier if not already known. This skill only works with existing pipelines.
Call MCP tool: harness_get
Parameters:
resource_type: "pipeline"
resource_id: "<pipeline_identifier>"
org_id: "<organization>"
project_id: "<project>"
Step 2: Analyze Pipeline Structure
Parse the pipeline YAML to identify:
- All stages and their types (
CI,SecurityTests,Deployment,Approval) - Whether a
SecurityTestsstage already exists - Existing steps in each stage
Present the structure to the user:
Pipeline: <name>
Stage 1: <stage_name> (type: <stage_type>)
- Step 1: <step_name> (type: <step_type>)
...
Ask the user where they want the scanner step added:
Present the available insertion points:
- Any existing
CIstage (scanner step is added directly into that stage'sexecution.steps) - Any existing
SecurityTestsstage (scanner step is added into that stage'sexecution.steps) - A new
SecurityTestsstage (appended to the pipeline if no suitable stage exists or user prefers isolation)
Recommendation guidance:
- Adding into an existing
CIstage — simpler, no extra infrastructure needed, scan runs as part of the build - Adding a new
SecurityTestsstage — isolated, runs independently, useful when scanning images built elsewhere or from a registry
If the user doesn't specify, default to adding inside the existing CI stage if one exists.
Step 3: Recommend Scanner Type
Present the available container image scanners supported in Harness STO:
Available Container Scanners:
- Harness SCA (default — native Harness container scanner, zero config)
- Aqua Trivy (open-source, broad OS and library coverage)
- Grype (open-source by Anchore, fast and accurate)
- Snyk (commercial, developer-friendly with fix advice)
- Prisma Cloud (commercial, enterprise runtime + image scanning)
- Anchore Enterprise (commercial, policy-based enforcement)
- Black Duck (commercial, license compliance + vulnerabilities)
- Wiz (commercial, cloud-native security)
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.
- 10d ago First seen · 484 lines · 176 tokens per session scan A 31635308dd66
configure-container-scan is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 19d ago), licensed Apache-2.0. It adds 176 tokens to every session and 4,157 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to configure-container-scan, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.