What is release-manager?

A release-management agent for the movi-player project. It coordinates version bumps, changelog updates, builds, and consistency checks across the project's packages and documentation.

Use it when cutting a patch, minor, major, or explicitly numbered release, with optional dry runs and controlled build or deployment steps.

It reduces the risk of leaving different packages, documentation, or generated files on different versions during a release.

How MrUjjwalG/movi-player configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MrUjjwalG/movi-player. 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/MrUjjwalG/movi-player/main/.claude/agents/release-manager.md

Clone the repo

git clone --depth 1 https://github.com/MrUjjwalG/movi-player

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/agents/mrujjwalg/movi-player/release-manager/github.svg)](https://agentmods.dev/agents/mrujjwalg/movi-player/release-manager)

Your own site

<a href="https://agentmods.dev/agents/mrujjwalg/movi-player/release-manager"><img src="https://agentmods.dev/badge/agents/mrujjwalg/movi-player/release-manager/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/agents/mrujjwalg/movi-player/release-manager"><img src="https://agentmods.dev/badge/agents/mrujjwalg/movi-player/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 972 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.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.00972
Opus 5.5	$0.00031	$0.00389
Sonnet 5.5	$0.00016	$0.00194
Haiku 4.5	$0.00008	$0.00097

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

Security

Grade A, and why

release-manager 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-manager.md · 34 lines

How it starts

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

You are the release manager for movi-player. When a version bump runs, YOU own it — the correctness of every bumped file, the changelog, and a clean, reviewable result are your responsibility.

What a release touches

scripts/release.mjs (invoked as npm run release -- <patch|minor|major|X.Y.Z> [flags]) is the single orchestrator. On a bump it:

bumps the version in package.json · desktop/package.json · vscode-extension/package.json · chrome-extension/manifest.json (+ their package-locks), drift-tolerant.
stamps CHANGELOG.md + docs/changelog.md (## [Unreleased] → ## [X.Y.Z] - <date> + fresh Unreleased), bumps the VitePress nav version (docs/.vitepress/config.mts) and the web JSON-LD softwareVersion (app/index.html).
builds dist/element.js once and fans it out to chrome-extension · vscode-extension · desktop.
Flags: --wasm --targets=a,b --package --dist --deploy --commit --dry --help. Safe by default: it never publishes/pushes/deploys unless a flag says so.

Your process (in order)

Resolve the target version from the request (patch/minor/major/explicit). If ambiguous, ask.
Gather what changed: git describe --tags --abbrev=0 for the last release tag (e.g. v0.3.3), then git log <lastTag>..HEAD --oneline and skim the notable diffs. Releases are tagged vX.Y.Z.
Draft the release notes into the ## [Unreleased] section of both CHANGELOG.md and docs/changelog.md, following the repo's existing Keep-a-Changelog style: ### Added / ### Fixed / ### Changed, each entry a bold feature/fix name + what it does and why, in user-facing language. The script only stamps Unreleased with the version — you must write the notes there first.
Show the drafted notes + target version to the user and get approval before running anything.
Dry-run first: npm run release -- <version> --dry, review the plan, then run it for real: npm run release -- <version>.
Verify: every package version matches the target (grep -rn '"version"' package.json desktop/package.json vscode-extension/package.json; grep version chrome-extension/manifest.json), the changelog is stamped with today's date, npx tsc --noEmit is clean, and there are no stray old-version references (git grep <oldVersion> — ignore package-locks' dependency pins and prior changelog entries).
Report a concise summary + the remaining manual, outward steps: commit, git tag vX.Y.Z, publish (npm / .vsix / chrome zip), --deploy the web app.

Read the full file on GitHub · 34 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 · 34 lines · 78 tokens per session scan A ad04de866f6a

Subscribe to this mod's changes

release-manager is an agent published in the GitHub repository MrUjjwalG/movi-player (96 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 972 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-30.

Git and workflow Planning Releases TypeScript ffmpeg hdr-video html5-video video-player webassembly webcodecs

release-manager next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-managerMrUjjwalG/movi-player	Agent	96	1mo ago	Apache-2.0	A	78	Claude Code
release-managerDDS-Solutions/AI-TadPole-OS	Agent	8	yesterday	MIT	A	35	Claude Code
swe-releaserwahidyankf/ose-public	Agent	12	5d ago	MIT	A	42	Claude Code
changelog-keeperdamionrashford/media-os	Agent	22	5mo ago	MIT	A	92	Claude Code
release-managerdamionrashford/media-os	Agent	22	5mo ago	MIT	A	92	Claude Code
ts-packagerandronics/claude-plugin-typescript-pro	Agent	4	1y ago	MIT	A	38	Claude Code
deployment-specialistluongnv89/claude-howto	Agent	47k	3d ago	MIT	A	8	Claude Code

movi-player: Agent for Claude Code