What is enforce-slsa?

A Harness pipeline skill that adds a step to verify SLSA provenance for an existing build or deployment pipeline. SLSA provenance is signed information about how an software artifact was produced; optional OPA policies can check that information.

Use it to add SLSA verification to CI, deployment, or security stages and optionally enforce policy rules against the provenance data.

It helps confirm that an artifact has the expected origin and build record before it reaches a later pipeline stage. It requires provenance to already exist and works only with existing pipelines.

enforce-slsa — Skill for Claude Code and Codex by harness

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.

Any agent

npx skills add harness/harness-skills --skill enforce-slsa

Clone the repo

git clone --depth 1 https://github.com/harness/harness-skills

Made for: Claude Code, Codex.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/harness/harness-skills/enforce-slsa/github.svg)](https://agentmods.dev/skills/harness/harness-skills/enforce-slsa)

Your own site

<a href="https://agentmods.dev/skills/harness/harness-skills/enforce-slsa"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/enforce-slsa/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/harness/harness-skills/enforce-slsa"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/enforce-slsa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 173 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Data Exfiltration · line 112
Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.

Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.

How audits are shown

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.1	$0.00173	$0.03098
Opus 5	$0.00086	$0.01549
Sonnet 5	$0.00035	$0.00620
Haiku 4.5	$0.00017	$0.00310

Measured 10d ago against content hash 49511f99ded7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

enforce-slsa 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

enforce-slsa — 100% identical, 0 lines differ

skills/enforce-slsa/SKILL.md · 306 lines

How it starts

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

Enforce SLSA

Add an SLSA Verification (SlsaVerification) step to an existing Harness pipeline. The step verifies SLSA provenance attestations (when enabled) and optionally evaluates OPA policy sets against provenance data.

This skill only works with existing pipelines — do not create standalone verification-only pipelines.

Prerequisites: SLSA provenance must already exist for the artifact (typically from a provenance step via /generate-slsa — UI label SLSA Generation). Optional policy sets for provenance enforcement (/create-policy, harness_list policy_set).

Supported stages: CI, CD (Deployment), and Security. CD requires a containerized step group. Unlike SBOM enforcement, CI and CD both use SlsaVerification (no separate CD step type).

Guide the user through a step-by-step interactive wizard (same UX as /generate-slsa):

Wizard: references/interactive-wizard-flow.md
UI ↔ YAML: references/slsa-verification-step.md
CD containerized step groups: skills/generate-slsa/references/cd-containerized-step-group.md

Interaction model (mandatory)

One question per turn — use AskQuestion when available; otherwise numbered options with (Recommended).
Opening message — add SLSA Verification; mention generation + optional policy prerequisites.
Progress breadcrumb — after pipeline fetch: Pipeline · Placement · Source · Details · Verify · Policy · Submit
Record answers — running summary; do not re-ask unless the user changes direction.
Fetch before configure — harness_get before placement/source questions.
Show pipeline structure — highlight provenance (SLSA Generation) and connectors.
Infer source from generation — when one provenance step exists (or identifier: slsageneration), reuse its source (map repo → image_path, lowercase → PascalCase types).
Never guess image tags — default from generation step; ask if ambiguous.
Confirm before write — summary + harness_update only after user confirms.
Stop after update — after successful harness_update, provide a configuration summary and point the user to /run-pipeline to execute. Do not call harness_execute, poll executions, or run harness_diagnose in this skill (same pattern as /configure-repo-scan).
CD on CI-only pipeline — do not reject CD verify; run Phase 3b to add Deploy stage + containerized group.
Verify method must match generation — keyless ↔ keyless, keybased ↔ public key from same key pair.

Read the full file on GitHub · 306 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

10d ago First seen · 306 lines · 173 tokens per session scan A 49511f99ded7

Subscribe to this mod's changes

enforce-slsa is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 173 tokens to every session and 3,098 once invoked, about $0.0009 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-30.

CI and CD DevOps and cloud Security agent-skills agents

github-actions-templates

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

wshobson/agents · 44 tokens

secrets-management

Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.

wshobson/agents · 39 tokens

deployment-pipeline-design

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.

wshobson/agents · 58 tokens

enforce-slsa