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.
npx agentmods add skills/seed-hypermedia/seed/run-releasenpx skills add seed-hypermedia/seed --skill run-releasegit clone --depth 1 https://github.com/seed-hypermedia/seedWrote 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.
[](https://agentmods.dev/skills/seed-hypermedia/seed/run-release)<a href="https://agentmods.dev/skills/seed-hypermedia/seed/run-release"><img src="https://agentmods.dev/badge/skills/seed-hypermedia/seed/run-release.svg" alt="Measured on agentmods" height="20"></a>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.00022 | $0.00879 |
| Opus 5 | $0.00011 | $0.00439 |
| Sonnet 5 | $0.00004 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
run-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Release
Execute the release process in docs/releasing.md. That doc is canonical for the process details;
this skill is the interactive runbook. Invoking this skill counts as explicit permission to create
and push the release tag, but confirm the version number with the user before pushing it.
Steps
- Preflight: confirm you are on
main, the working tree is clean, and localmainmatchesorigin/main. Abort and report if not. - Determine the version (
YYYY.M.N, seedocs/releasing.md): checkgit tag --sort=-creatordate | head -5. If the latest tag is from the current month, increment its last number; otherwise start at.1for the current month. - Verify CI is green for the commit BEFORE tagging. The release workflows gate on the same
frontend-tests(Lint, unit tests, e2e), so a red commit means a doomed release run and a re-tag. Check the existing result first — a push tomainalready triggeredDev - Docker Imageson this exact commit:gh run list --workflow "Dev - Docker Images" --branch main --limit 5 --json headSha,status,conclusion,databaseId- Green for the commit → proceed.
- Red → diagnose with
gh run view <id>; fix onmainfirst, then restart at step 1. - Still running or missing → don't wait for it; releases are often cut in a rush. Instead run
the most obvious, fastest checks locally and then tag. In order of cost-effectiveness:
- Root
pnpm format:check(~1 min; the most common release-killer). The root script chains pnpm workspaces, thenagents/, thenvault/with&&— later groups are masked until earlier ones pass, so only the root script proves all of them. - Unit tests for packages touched since the last green CI run (e.g.
cd frontend/apps/desktop && pnpm exec vitest run;cd agents && bun test). - Skip slow suites (e2e, backend, builds) — the release workflow runs full CI anyway; the local pass only exists to avoid tagging a commit that is dead on arrival.
- Root
- Confirm the version and the commit to be tagged with the user.
- Tag and push:
git tag <version> && git push origin <version>. - Wait for the release workflows (
Release - Desktop App,Release - Docker Images) to go green:gh run list --workflow release-desktop.yml, thengh run watch <run-id>. Builds take tens of minutes — keep waiting, don't proceed early. If a workflow fails, stop and report. - Draft release notes for
<prev-tag>..<version>following the voice, grouping, and exclusion rules in thereleasenotesskill, but match the exact format of the last few published releases (gh release view <prev-tag>). Key rules fromdocs/releasing.md:- Very short feature entries; many commits often collapse into one line.
- No entries for regressions introduced and fixed since the previous tag — never released, users never saw them.
- End with the
**Full Changelog**compare link.
- Show the draft to the user and apply their edits, then publish:
gh release edit <version> --notes-file <tmpfile> --prerelease=false --latest(the workflow creates the release as a prerelease; this promotes it). - Publish latest.json so desktop auto-update sees the release:
gh workflow run "Generate latest.json (prod)"and confirm the run succeeds. - Report: version, release URL, and the state of each step.
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.
- 3d ago First seen · 53 lines · 22 tokens per session scan A 87ca97b0e62c
run-release is a skill published in the GitHub repository seed-hypermedia/seed (56 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 879 once invoked, about $0.0001 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.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
multi-repo-release
Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".