What is generate-slsa?

A guided step for adding SLSA provenance to an existing Harness pipeline. SLSA provenance is a record of how a software artifact, such as a container image, was built; the step can also create a Cosign attestation.

Adding the provenance step after an image build or push, choosing keyless, key-based, or Vault signing, and configuring supported container registries or Harness artifacts.

It ensures provenance is added only after an image is built and pushed, and guides the required Harness configuration choices.

generate-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 generate-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/generate-slsa/github.svg)](https://agentmods.dev/skills/harness/harness-skills/generate-slsa)

Your own site

<a href="https://agentmods.dev/skills/harness/harness-skills/generate-slsa"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/generate-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/generate-slsa"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/generate-slsa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,944 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 pass 7 Sept 2026

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.00180	$0.02944
Opus 5	$0.00090	$0.01472
Sonnet 5	$0.00036	$0.00589
Haiku 4.5	$0.00018	$0.00294

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

Security

Grade A, and why

generate-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:

generate-slsa — 100% identical, 0 lines differ

skills/generate-slsa/SKILL.md · 303 lines

How it starts

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

Generate SLSA

Add a SLSA Generation step to an existing Harness pipeline to generate SLSA provenance and optionally attest/sign the .att file in the container registry. Pipeline YAML uses type: provenance (UI label: SLSA Generation; do not use SlsaGeneration — API rejects it).

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

Prerequisites: Image must be built and pushed (or available in registry) before SLSA runs. Key-based attestation requires Cosign key pair secrets (/create-secret). Harness Cloud builds enable SLSA Level 3 provenance when using hosted infrastructure.

Guide the user through a step-by-step interactive wizard (same UX as /configure-repo-scan):

Wizard: references/interactive-wizard-flow.md
UI ↔ YAML: references/slsa-generation-step.md
CD containerized step groups: 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 Generation after image build/push; mention attestation options.
Progress breadcrumb — after pipeline fetch: Pipeline · Placement · Source · Details · Attestation · 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 build/push steps and existing provenance / SscaOrchestration steps (UI: SLSA Generation).
Infer connector from build/push — skip connector question when unambiguous from YAML.
Never guess image tags — always ask for image/repo in Phase 7.
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).
Phase 3 Placement is mandatory — always run Phase 2 then Phase 3, even with one CI stage or prior session context.
Sequential with SBOM — if SscaOrchestration exists, place SLSA after it; never parallel (Cosign race).
CD path — Deploy stage steps go inside containerized stepGroup only — see CD reference.

Read the full file on GitHub · 303 lines

Files

What ships with it

3 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 · 303 lines · 180 tokens per session scan A 48fc57b8768f

Subscribe to this mod's changes

generate-slsa is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed today), licensed Apache-2.0. It adds 180 tokens to every session and 2,944 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.

Containers 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

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…

omnigent-ai/omnigent · 84 tokens

azure-containerregistry-py

Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories. Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".

microsoft/skills · 48 tokens

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…

microsoft/skills · 166 tokens

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…

microsoft/skills · 106 tokens

wrangler

Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, deployment, and Cloudflare resource management.

cloudflare/skills · 25 tokens