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 commands/mrujjwalg/movi-player/releasegit 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/commands/mrujjwalg/movi-player/release)<a href="https://agentmods.dev/commands/mrujjwalg/movi-player/release"><img src="https://agentmods.dev/badge/commands/mrujjwalg/movi-player/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.1 | $0.00016 | $0.00229 |
| Opus 5 | $0.00008 | $0.00114 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
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 6d 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.
What it actually says
Hand this release off to the release-manager subagent — it takes full responsibility for the bump.
Target: $ARGUMENTS (if empty, ask which of patch / minor / major / explicit version).
Spawn the release-manager agent (via the Agent tool, subagent_type: "release-manager") and have it run its full process: draft the CHANGELOG ## [Unreleased] notes from git log <last-tag>..HEAD in both CHANGELOG.md and docs/changelog.md, get your approval on the notes + version, dry-run npm run release -- <version>, then run it for real, and verify every package / doc / target bumped consistently.
Relay the agent's drafted notes and its final report back to me. Do not commit, tag, push, publish, or deploy unless I explicitly approve that 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.
- 6d ago First seen · 13 lines · 16 tokens per session scan A 67e69711cf44
release is a command published in the GitHub repository MrUjjwalG/movi-player (48 stars, last pushed 13d ago), licensed Apache-2.0. It adds 16 tokens to every session and 229 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-30.
Other commands, from other repositories
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.