fold: Agent for Claude Code

.claude/agents/release-verifier.md

release-verifier is an agent for Claude Code from fold-run/fold. It costs 74 tokens per session (1,141 once invoked), scanned A, original, Apache-2.0.

A read-only checker for a published software release. It verifies that downloadable files, checksums, container images, an OCI chart, software bills of materials, signatures, and build attestations exist and agree.

In plain words
What is it for?
Checking a tagged fold release end to end, including archives, cryptographic signatures, SBOMs, container images, charts, and Sigstore attestations.
Why use it?
A successful release workflow only shows that the jobs finished; it does not prove that users can retrieve and verify every published artifact. This check exposes missing or mismatched release outputs before announcement.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is fold-run/fold's own configuration. It tells Claude Code how to work on fold itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything fold configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fold-run/fold. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fold-run/fold/main/.claude/agents/release-verifier.md
Clone the repo
git clone --depth 1 https://github.com/fold-run/fold

Made for: Claude Code.

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.

agentmods badge for release-verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/fold-run/fold/release-verifier/github.svg)](https://agentmods.dev/agents/fold-run/fold/release-verifier)
Your own site
<a href="https://agentmods.dev/agents/fold-run/fold/release-verifier"><img src="https://agentmods.dev/badge/agents/fold-run/fold/release-verifier/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.

agentmods 80×15 button for release-verifier

Your own site · 80×15
<a href="https://agentmods.dev/agents/fold-run/fold/release-verifier"><img src="https://agentmods.dev/badge/agents/fold-run/fold/release-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,141 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01141
Opus 5.5 $0.00030 $0.00456
Sonnet 5.5 $0.00015 $0.00228
Haiku 4.5 $0.00007 $0.00114

Measured 2mo ago against content hash 8df7f4fe4663, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-verifier 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 2mo 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.

.claude/agents/release-verifier.md · 88 lines

How it starts

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

You verify that a published fold release is what it claims to be, from the position of an operator who has never seen this repository. You are read-only: you check, you report, you do not fix. A green release workflow says the jobs succeeded; you say whether the artifacts exist, verify, and agree with each other.

Take the version from the caller, or use the newest tag (git ls-remote --tags origin | tail). Report a table of checks with pass/fail and the real command output for every failure. Never report a check as passing if you could not run it — say the tool is missing instead.

What a release publishes

Three jobs, three artifact families, all in .github/workflows/release.yml:

  • binaries (goreleaser) — archives for fold (linux, darwin × amd64, arm64), fold-discovery (linux only), fold-stdio and fold-registry (linux, darwin); checksums.txt; a keyless cosign signature and certificate on the checksum file; SBOMs per archive; a build-provenance attestation.
  • image — ghcr.io/fold-run/fold, ghcr.io/fold-run/fold-discovery, ghcr.io/fold-run/fold-stdio, ghcr.io/fold-run/fold-registry, each at the tag and at latest, each with in-registry provenance and SBOM, each with a sigstore attestation on its digest.
  • chart — oci://ghcr.io/fold-run/charts/fold at the chart's own version (not the gateway version), attested the same way.

The checks

Attestations — the toolchain an operator or admission controller uses:

gh attestation verify oci://ghcr.io/fold-run/fold:vX.Y.Z --owner fold-run
gh attestation verify oci://ghcr.io/fold-run/fold-discovery:vX.Y.Z --owner fold-run
gh attestation verify oci://ghcr.io/fold-run/fold-stdio:vX.Y.Z --owner fold-run
gh attestation verify oci://ghcr.io/fold-run/fold-registry:vX.Y.Z --owner fold-run
# The chart's tag is not optional: the chart repo publishes no :latest, so
# an untagged reference resolves to one and fails MANIFEST_UNKNOWN — which
# reads exactly like a missing attestation and is not one.
gh attestation verify oci://ghcr.io/fold-run/charts/fold:<chart-version> --owner fold-run

Read the full file on GitHub · 88 lines

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.

  1. 2mo ago First seen · 88 lines · 74 tokens per session scan A 8df7f4fe4663

Subscribe to this mod's changes

release-verifier is an agent published in the GitHub repository fold-run/fold (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,141 once invoked, about $0.0003 per session on Opus 5.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-31.

Related

release-verifier compared with agents from other repositories

release-verifier next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-verifierfold-run/foldAgent112d agoApache-2.0A74Claude Code
conflict-resolverlugassawan/swe-workbenchAgent32d agoMITA40Claude Code
redundancy-assessorlugassawan/swe-workbenchAgent32d agoMITA38Claude Code
release-engineerGoldziher/ai-rulezAgent167yesterdayMITA19Claude Code
release-managerOrodruinLabs/nazgulAgent72mo agononeA21Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code