A pipeline step that checks whether a container or other software artifact has a valid Cosign signature. Cosign is a tool used to sign software so its origin and integrity can be checked.

Use it to add signature verification to an existing Harness pipeline in a CI, security, or container-based deployment stage.

It helps detect artifacts that were not signed by the expected key before they move through a build, security check, or deployment.

verify-sign — 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 verify-sign

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

Your own site

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

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

When invoked 4,102 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 195
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.00144	$0.04102
Opus 5	$0.00072	$0.02051
Sonnet 5	$0.00029	$0.00820
Haiku 4.5	$0.00014	$0.00410

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

Security

Grade A, and why

verify-sign 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 11d 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:

verify-sign — 100% identical, 0 lines differ

skills/verify-sign/SKILL.md · 420 lines

How it starts

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

Verify Sign

Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline. The step verifies Cosign signatures on artifacts — typically immediately after SscaArtifactSigning.

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

Prerequisites: Artifact must already be signed (typically via /sign-artifact / SscaArtifactSigning). Key-based verify requires the Cosign public key file secret matching the signing private key (/create-secret). If signing did not upload .sig to the registry, Harness pulls the signature from its database during verification.

Supported stages: CI, Security, and CD (Deployment in containerized step group before deploy).

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

Wizard: references/interactive-wizard-flow.md
UI ↔ YAML: references/artifact-verification-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 Artifact Verification; mention signing prerequisite + HAR support.
Progress breadcrumb — after pipeline fetch: Pipeline · Placement · Source · Details · Verify · 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 SscaArtifactSigning and connectors.
Infer source from signing — when one SscaArtifactSigning step exists, reuse its source. If multiple exist, ask which step to mirror.
Never guess image tags — default from signing 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 signing — keyless ↔ keyless, keybased/cosign ↔ public key from same key pair.
Offer all three source tiles — Third-Party, HAR, and Harness Local Stage.
List all connectors in Phase 6 — same rules as /sign-artifact: harness_list with filters.type, all scopes, size: 100, paginate; never hand-pick a subset. See wizard Phase 6.
List all infrastructure in Phase 3b — harness_list per environment with filters.environment_id; never show only the infra for one pre-selected environment.
CD image defaults to <+artifact.image> — for Deploy-stage verify, recommend the service artifact expression over a static tag from signing. Warn when static image ≠ service default tag.
Preflight delegates before CD update — harness_list(resource_type="delegate") or harness_execute(test_connection) on the K8s connector used in stepGroupInfra. Abort or warn if DELEGATE_NOT_AVAILABLE is likely (connector has delegateSelectors with no active delegate).
CD Deploy stage YAML requirements — new Deploy stages need failureStrategies: StageRollback, rollbackSteps with K8sRollingRollback + spec: {}, and CI stages need MarkAsFailure when missing. See references/cd-containerized-step-group.md.

Read the full file on GitHub · 420 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.

11d ago First seen · 420 lines · 144 tokens per session scan A ae98224ea2da

Subscribe to this mod's changes

verify-sign is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 144 tokens to every session and 4,102 once invoked, about $0.0007 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

verify-sign