What is generate-slsa?

A skill that adds a SLSA provenance step to an existing Harness pipeline. SLSA is a standard way to record how software was built, and Cosign can sign that record.

Use it after building and pushing Docker or other supported container images in Harness. It can generate provenance and optionally create an attestation with Cosign.

It helps preserve evidence about a container image’s build process and can attach that evidence to the image in a registry.

generate-slsa — Skill for Claude Code 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-ai --skill generate-slsa

Clone the repo

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

Made for: Claude Code.

Or install harness, the plugin that ships this one along with the rest of its 55 skills, 1 MCP server.

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

Your own site

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

Origin 100% copy Near-identical to another mod 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 8d ago against content hash 48fc57b8768f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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

This is a copy

100% identical to generate-slsa — 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.

plugins/claude/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.

8d 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-ai (19 stars, last pushed 17d ago), 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. It is 100% identical to generate-slsa, differing in 0 lines, and is treated as a copy.

CI and CD DevOps and cloud Security

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens