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.
curl -O https://raw.githubusercontent.com/MrUjjwalG/movi-player/main/.claude/agents/release-manager.mdgit clone --depth 1 https://github.com/MrUjjwalG/movi-playerWrote 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/agents/mrujjwalg/movi-player/release-manager)<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="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.1 | $0.00078 | $0.00972 |
| Opus 5 | $0.00039 | $0.00486 |
| Sonnet 5 | $0.00016 | $0.00194 |
| Haiku 4.5 | $0.00008 | $0.00097 |
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 7d 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 — 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-LDsoftwareVersion(app/index.html). - builds
dist/element.jsonce 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=0for the last release tag (e.g.v0.3.3), thengit log <lastTag>..HEAD --onelineand skim the notable diffs. Releases are taggedvX.Y.Z. - Draft the release notes into the
## [Unreleased]section of bothCHANGELOG.mdanddocs/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 --noEmitis 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),--deploythe web app.
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.
- 7d ago First seen · 34 lines · 78 tokens per session scan A ad04de866f6a
release-manager is an agent published in the GitHub repository MrUjjwalG/movi-player (49 stars, last pushed 14d ago), licensed Apache-2.0. It adds 78 tokens to every session and 972 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-30.
Other agents, from other repositories
changelog-keeper
Maintains CHANGELOG.md following Keep a Changelog 1.1.0 + Semantic Versioning 2.0.0. Categorizes changes into Added / Changed / Deprecated / Removed / Fixed / Security. Keeps an Unreleased section up to date as commits land. Use when the user says "update the changelog", "log this change", "what's changed", or when a…
release-manager
Manages media-os plugin releases. Bumps semver in plugin.json + marketplace.json + CHANGELOG.md, creates a git tag, cuts a GitHub release with auto-generated release notes derived from commits since the previous tag. Use proactively when the user says "cut a release", "tag v1.0.0", "ship the new version", "prepare…
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.