What is fold-release?

A release procedure for fold, including checks, changelog updates, version changes, publishing, and verification. A release is started by pushing a specially named Git tag, which triggers the build workflow.

Use it when preparing and publishing a fold release, including checking code, updating the Helm chart version, watching CI, and verifying artifacts.

It reduces the risk of publishing an untested build or skipping required approval before Git changes and release actions.

fold-release — Skill for Claude Code and Codex by fold-run: A release procedure for fold, including checks, changelog updates…

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.

agentmods

npx agentmods add skills/fold-run/fold/fold-release

Any agent

npx skills add fold-run/fold --skill fold-release

Clone the repo

git clone --depth 1 https://github.com/fold-run/fold

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/fold-run/fold/fold-release.svg)](https://agentmods.dev/skills/fold-run/fold/fold-release)

Your own site

<a href="https://agentmods.dev/skills/fold-run/fold/fold-release"><img src="https://agentmods.dev/badge/skills/fold-run/fold/fold-release.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 2,074 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00081	$0.02074
Opus 5	$0.00041	$0.01037
Sonnet 5	$0.00016	$0.00415
Haiku 4.5	$0.00008	$0.00207

Measured today against content hash e9dd5e987de4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fold-release 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 today.

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/skills/fold-release/SKILL.md · 158 lines

How it starts

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

fold release workflow

Releases are annotated-tag-driven: pushing vX.Y.Z triggers .github/workflows/release.yml (goreleaser). The version string is stamped via -ldflags "-X github.com/fold-run/fold/gateway.ldflagsVersion=..." — goreleaser handles this; never hardcode a version in source.

Cardinal rule: every git-touching step needs the user's explicit, per-step approval. "Release it" authorizes the process, not each push. Finish and report each step, then wait for the go-ahead before the next. Never batch commit+push+tag on a single approval.

Steps

Verify before anything touches git. Run the full gate:
- make check (fmt-check, tidy-check, vet, build, race, lint)
- make bench if the proxy path changed (gate: added p50 < 5 ms)
- make conformance if behavior through the gateway changed (40/40)
- make helm-check if deploy/helm/ changed Report results with real output. Stop here if anything fails.
Bump the console pin. gateway/console is vendored from fold-run/fold-console at the commit in scripts/sync-console.sh, and nothing bumps it on a schedule any more — console-sync.yml is workflow_dispatch only, because the weekly robot generated more repair work than console changes. The release is where a human is already reading a diff, so it is where the pin moves.
```
git ls-remote https://github.com/fold-run/fold-console.git refs/heads/main
```
If that SHA differs from CONSOLE_COMMIT, re-vendor and re-verify — the assets are a supply-chain input, so this is a real review, not a rubber stamp:
```
CONSOLE_COMMIT=<40-hex> make sync-console
git diff --stat -- gateway/console      # read what changed
make console-check && make test
```
Then run the security-auditor agent over the diff, as the workflow's own PR body demands. If the console has not moved, say so and continue — a release with a stale-but-current pin is normal.
Pick the version. The repo is under the v1 compatibility contract (README "API stability"): patch for fixes, minor for backwards-compatible features, major only for a deliberate contract break (which needs its own conversation). Confirm the number with the user.

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

today Changed · +25 lines e9dd5e987de4
4d ago First seen · 133 lines · 81 tokens per session scan A c37b92ada032

Subscribe to this mod's changes

fold-release is a skill published in the GitHub repository fold-run/fold (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 81 tokens to every session and 2,074 once invoked, about $0.0004 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-31.

DevOps and cloud Git and workflow Go ai api-gateway federation gateway go

release-notes

Draft concise release notes.

ollama/ollama · 9 tokens

use-modern-go

Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.

JetBrains/go-modern-guidelines · 32 tokens

jwx-guide-v4

Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns. For developers using jwx, not for developing the library itself.

lestrrat-go/jwx · 61 tokens

jwx-companion-bulk

Apply bulk operations across all jwx companion modules. Args.

lestrrat-go/jwx · 0 tokens

readme-generate

從原始碼分析自動生成雙語 README。當使用者請求為專案建立 README、需要從程式碼庫生成 README.md（英文）和 README.zh.md（中文）、或希望為其函式庫/套件建立一致的多語言文件時使用。.

agenvoy/Agenvoy · 67 tokens

search-suitable-public-api

Search the curated Agenvoy public API list for an API that fits the current user need or skill context, then chain into the api-tool-add skill to register it under /.config/agenvoy/tools/api/. Triggers when the agent lacks a tool for a data lookup (weather, currency, geocoding, dictionary, etc.), when the user says…

agenvoy/Agenvoy · 131 tokens