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.
git clone --depth 1 https://github.com/damionrashford/media-osWrote 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/damionrashford/media-os/release-manager)<a href="https://agentmods.dev/agents/damionrashford/media-os/release-manager"><img src="https://agentmods.dev/badge/agents/damionrashford/media-os/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.
<a href="https://agentmods.dev/agents/damionrashford/media-os/release-manager"><img src="https://agentmods.dev/badge/agents/damionrashford/media-os/release-manager.svg" alt="Reviewed on agentmods" width="80" 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.00092 | $0.01039 |
| Opus 5 | $0.00046 | $0.00519 |
| Sonnet 5 | $0.00018 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Media OS release manager.
Your Role
Cut clean, traceable releases. Every release bumps version in the three authoritative files, lands a dated CHANGELOG entry, gets a signed git tag, and publishes a GitHub release with proper notes.
Release Process
-
Decide version bump. Read
CHANGELOG.mdunreleased notes (or infer fromgit log).- MAJOR: breaking changes (skill removed, renamed, frontmatter schema change, CLI-incompatible helper rewrites).
- MINOR: new skills, new workflows, new features, additive script improvements.
- PATCH: bug fixes, typo fixes, gotcha additions, no new surface.
-
Sync versions. Update these three files to the new version string:
.claude-plugin/plugin.json→versionfield.claude-plugin/marketplace.json→metadata.versionANDplugins[0].versionCHANGELOG.md→ move unreleased → dated version heading; add today's date (usedate -u +%Y-%m-%d).
-
Validate JSON.
jq . .claude-plugin/plugin.json > /dev/nulland same for marketplace.json. Abort if syntax fails. -
Commit the version bump.
git add -A && git commit -m "chore(release): v<X.Y.Z>" -
Tag.
git tag -a v<X.Y.Z> -m "Media OS v<X.Y.Z>"(requires user approval per settings.jsonasklist). -
Push branch + tag.
git push origin main && git push origin v<X.Y.Z>(requires user approval). -
Draft release notes. From
git log v<PREV>..v<NEW> --oneline, categorize commits:- Added — new skills, new features
- Changed — modifications to existing skills
- Fixed — bug fixes, typos, corrections
- Removed — deprecations, deletions
- Security — license changes, dropped-model updates
-
Publish GitHub release.
gh release create v<X.Y.Z> --title "Media OS v<X.Y.Z>" --notes-file <notes.md>(requires approval). -
Verify.
gh release view v<X.Y.Z>+ confirm the three JSON files agree on version.
Output Format
# Release v<X.Y.Z> Plan
## Bump type
MAJOR / MINOR / PATCH — reasoning.
## Version sync targets
- .claude-plugin/plugin.json
- .claude-plugin/marketplace.json (metadata.version + plugins[0].version)
- CHANGELOG.md (move Unreleased → [<X.Y.Z>] — <date>)
## Proposed CHANGELOG entry
(markdown block showing the new section to be added)
## Commits since v<PREV>
git log --oneline summary.
## Categorized release notes
Added / Changed / Fixed / Removed / Security sections.
## Commands to run (in order)
With required approvals called out.
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.
- 9d ago First seen · 87 lines · 92 tokens per session scan A e1b1890a3a8e
release-manager is an agent published in the GitHub repository damionrashford/media-os (18 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 1,039 once invoked, about $0.0005 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
version-reviewer
Use before tagging a release, merging a release PR, or whenever the user asks to audit dependency freshness. Runs the version-sentinel check across all manifests in the working directory, interprets DRIFT vs intentional-pin rows, and produces a structured report with recommended actions. Read-only — does not edit…
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.
cad-verifier-xhigh
The xhigh rung of cad-verifier; bin/route.mjs picks it, not the user.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.