Enforce Slsa

What it does

When your agent uses it

• Asked to verify SLSA
• Enforce SLSA policies
• Add SLSA verification step
• Validate SLSA attestation

Example prompts

• “/enforce-slsa”

Requirements

• Docker
• Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2)

Workflow steps

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

1. 1One question per turn — use AskQuestion when available; otherwise numbered options with (Recommended).
2. 2Opening message — add SLSA Verification; mention generation + optional policy prerequisites.
3. 3Progress breadcrumb — after pipeline fetch
4. 4Record answers — running summary; do not re-ask unless the user changes direction.
5. 5Fetch before configure — harness_get before placement/source questions.
6. 6Show pipeline structure — highlight provenance (SLSA Generation) and connectors.
7. 7Infer source from generation — when one provenance step exists (or identifier: slsageneration), reuse its source (map repo → image_path…
8. 8Never guess image tags — default from generation step; ask if ambiguous.
9. 9Confirm before write — summary + harness_update only after user confirms.
10. 10Stop after update — after successful harness_update, provide a configuration summary and
11. 11CD on CI-only pipeline — do not reject CD verify; run Phase 3b to add Deploy stage + containerized group.
12. 12Verify method must match generation — keyless ↔ keyless, keybased ↔ public key from same key pair.

What it can do on your machine

Read from SKILL.md and the folder at commit c25faee. 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

  No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

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

• Network

  No URLs in SKILL.md.

  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.

• Compatibility

  Requires Harness MCP v2 server (harness-mcp-v2)

  From compatibility in the SKILL.md frontmatter.

Context cost

Enforce Slsa loads about 3.2k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 179 tokens; SKILL.md has 1,085 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~179

When it runs · the whole SKILL.md, loaded when a task matches

~3.2k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~5.8k

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

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

The full file from harness/harness-skills at commit c25faee, republished under its Apache-2.0 licence (© harness). 1,085 words, ~3,155 tokens.

name

enforce-slsa

description

Add an SLSA Verification (SlsaVerification) step to an existing Harness pipeline to verify SLSA provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification step, validate SLSA attestation, or gate deploy on SLSA provenance. Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement, SlsaVerification, verify SLSA attestation, add SLSA verify step.

compatibility

Requires Harness MCP v2 server (harness-mcp-v2)

metadata.author

Harness

metadata.version

1.0.0

metadata.mcp-server

harness-mcp-v2

license

Apache-2.0

- step:
    identifier: slsaverification
    name: SLSA Verification
    type: SlsaVerification
    spec:
      source:
        type: Docker
        spec:
          connector: lavakush07
          image_path: lavakush07/easy-buggy-app:blog
      verify_attestation:
        type: keyless
        spec:
          oidcProvider: harness
    timeout: 15m

      verify_attestation:
        type: keybased
        spec:
          publicKey: account.cosign_public_key

    enforce:
      policySets:
        - slsa_provenance_rules

harness_update
  resource_type: pipeline
  resource_id: <pipeline_identifier>
  org_id: <organization>
  project_id: <project>
  body: { yamlPipeline: "<updated pipeline YAML>" }

## SLSA Verification Configured

**Pipeline:** <pipeline_name>
**Step:** SLSA Verification (SlsaVerification)
**Location:** Stage "<stage_name>", <position>
**Source:** Docker — <connector> — <image_path>
**Verify attestation:** Keyless (Harness OIDC) — or as configured
**Policy sets:** <list or none>

**Pipeline URL:** https://app.harness.io/ng/account/<account_id>/module/ci/orgs/<org_id>/projects/<project_id>/pipelines/<pipeline_id>/pipeline-studio/

**Note:** Review the SLSA Verification step in Pipeline Studio to adjust Advanced settings.

### Next Steps
1. Run the pipeline via `/run-pipeline` to verify SLSA verification executes successfully
2. If the run fails, diagnose with `/debug-pipeline`
3. View verification outcome on the execution **Supply Chain** tab
4. If **Failed** due to policy deny, tune policies via `/create-policy`
5. Add generation with `/generate-slsa` if provenance was missing
6. Automate with `/create-trigger`

/enforce-slsa
Add SLSA verification after slsa-generation — keyless verify, policy set slsa_prod_rules

/enforce-slsa
Verify SLSA in deploy stage before K8s rolling deploy for easy-buggy-app:blog

/enforce-slsa
Verify SLSA with public key account.cosign_public_key — same image as generation step

© harness, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/enforce-slsa of harness/harness-skills.

• SKILL.md
• references/interactive-wizard-flow.md
• references/slsa-verification-step.md

Open the folder on GitHubat commit c25faee