A release workflow for publishing a new version of EverOS, a Python package, to PyPI, the main public package registry for Python. It uses a version tag to start automated checks and publishing, followed by a GitHub Release that must be published separately.

Use it to bump a package version, prepare its changelog, publish it to PyPI, and finish the associated GitHub release.

It turns versioning, changelog updates, package publishing, and release notes into a defined sequence with checks and approval points.

How EverMind-AI/EverOS configures Claude Code

About the project

EverOS is a Python library and local-first memory runtime that gives AI agents a portable memory layer across apps, devices, and workflows. It stores conversations, files, and agent activity as readable Markdown while maintaining local indexes for retrieval and reuse. The catalogue add-ons provide commands, skills, hooks, and settings for using EverOS with coding agents.

EverMind-AI/EverOS · 13,824 stars · on GitHub · evermind.ai

Reuse

Borrowing it

Nothing to install: this file belongs to EverMind-AI/EverOS. 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/EverMind-AI/EverOS/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/EverMind-AI/EverOS

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/evermind-ai/everos/release/github.svg)](https://agentmods.dev/skills/evermind-ai/everos/release)

Your own site

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

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

When invoked 1,341 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 pass 7 Sept 2026

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.00020	$0.01341
Opus 5.5	$0.00008	$0.00536
Sonnet 5.5	$0.00004	$0.00268
Haiku 4.5	$0.00002	$0.00134

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

Security

Grade A, and why

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

How it starts

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

/release

Publish a new version of everos to PyPI. Publishing is automated: pushing a vX.Y.Z tag triggers .github/workflows/release.yml, which builds, smoke-tests, and uploads via PyPI Trusted Publishing (OIDC — no stored token) behind the release environment's manual-approval gate, then drafts the GitHub Release page from the CHANGELOG.

A release is not finished when PyPI accepts the upload: the GitHub Release page is drafted, never auto-published, and someone has to write its lead summary and click Publish.

Preconditions

On main, up to date, with green CI (the tag builds from main's tree).
Decide the version per SemVer: patch = fixes, minor = back-compatible features, major = breaking changes.

Steps

1. Bump the version    → pyproject.toml [project] version = "X.Y.Z"
   (single source; everos.__version__ reads installed package metadata)
2. Update CHANGELOG.md → move the Unreleased entries under a new
   ## [X.Y.Z] - <date> heading, and write the release page's prose here
   (lead paragraph + `### Upgrade` group — see "The release page")
3. Commit              → git commit -m "chore(release): vX.Y.Z"
4. Open a PR, merge to main after green CI
5. Tag main + push     → git tag -a vX.Y.Z -m "vX.Y.Z" && git push origin vX.Y.Z
6. Approve             → the release.yml run pauses on the `release`
   environment; a reviewer approves in the Actions run
7. Verify              → https://pypi.org/project/everos/X.Y.Z/
8. Publish the page    → the run leaves a DRAFT GitHub Release, already
   complete if step 2 was done properly. Read it once, click Publish.

The tag must equal the pyproject.toml version — the workflow refuses to publish on a mismatch. A stable tag with no matching ## [X.Y.Z] CHANGELOG section fails the release job for the same reason.

The release page

The whole page is written in CHANGELOG.md, during the release PR. Nothing is meant to be composed at publish time — by then the changes are weeks old and the text gets no review. Write the version section like this:

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

2mo ago First seen · 120 lines · 20 tokens per session scan A 44771f7e551f

Subscribe to this mod's changes

release is a skill published in the GitHub repository EverMind-AI/EverOS (13,824 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 1,341 once invoked, about $0.0001 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-30.

Git and workflow LLM Memory and context Productivity agentic-ai ai chats long-term-memory

release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseEverMind-AI/EverOS	Skill	14k	yesterday	Apache-2.0	A	20	Claude Code
computer-historyMemTensor/memmy-agent	Skill	2.2k	today	MIT	A	42	Claude Code, Codex
computer-useMemTensor/memmy-agent	Skill	2.2k	today	MIT	A	37	Claude Code, Codex
githubMemTensor/memmy-agent	Skill	2.2k	today	MIT	A	44	Claude Code, Codex
cronMemTensor/memmy-agent	Skill	2.2k	today	MIT	A	8	Claude Code, Codex
GitHub PR Workflowagentic-in/elephant-agent	Skill	584	2mo ago	none	A	29	Claude Code, Codex
docxMemTensor/memmy-agent	Skill	2.2k	today	MIT	A	40	Claude Code, Codex

EverOS: Skill for Claude Code