Borrowing it
Nothing to install: this file belongs to BlaiseMoses01/playback-mcp. 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/BlaiseMoses01/playback-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/BlaiseMoses01/playback-mcpWrote 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/skills/blaisemoses01/playback-mcp/release)<a href="https://agentmods.dev/skills/blaisemoses01/playback-mcp/release"><img src="https://agentmods.dev/badge/skills/blaisemoses01/playback-mcp/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.00041 | $0.00854 |
| Opus 5 | $0.00020 | $0.00427 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing playback-mcp
Only server/ is published to npm (as playback-mcp); the extension is built and
attached to the GitHub Release as a zip. .github/workflows/publish.yml does the actual
publishing — it triggers on a published GitHub Release and expects the version to
already be bumped and merged into main beforehand.
Full narrative version of this lives in CONTRIBUTING.md's "Releasing" section — keep
both in sync if the process changes.
1. Pick the version
Semver. This project is pre-1.0, so treat it like 0.y.z: backwards-compatible
additions bump the minor (0.1.0 → 0.2.0), fixes bump the patch.
2. Prep the release commit on dev
-
Bump the version in the two places it's declared (grep the old version string to confirm none were missed):
"version"inserver/package.json"version"inextension/manifest.json(whatchrome://extensionsshows)
The
McpServerversion reported over MCP is no longer hardcoded —server/src/index.tsreadspkg.versionat startup, so it tracksserver/package.jsonautomatically. Andpnpm-lock.yamldoesn't record the workspace package's own version, so there's no lockfile step:pnpm install --frozen-lockfilestill passes after a bump. -
In
CHANGELOG.md: rename## [Unreleased]to## [X.Y.Z] - YYYY-MM-DD, add a fresh empty## [Unreleased]above it, and update the link refs at the bottom:[Unreleased]: https://github.com/BlaiseMoses01/playback-mcp/compare/vX.Y.Z...HEAD [X.Y.Z]: https://github.com/BlaiseMoses01/playback-mcp/releases/tag/vX.Y.Z -
Run the full gate:
pnpm run lint && pnpm run format:check && pnpm run typecheck && pnpm run build && pnpm test. -
Commit as
release: playback-mcp vX.Y.Z(see9a1ca94,07ed42afor precedent). -
git push origin dev.
3. PR dev into main
Use the pr skill. Wait for CI to go green, confirm with the user, then merge with
gh pr merge <number> --merge.
4. Tag and publish
From main, after the merge:
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 · 74 lines · 41 tokens per session scan A 689fa24e5f03
release is a skill published in the GitHub repository BlaiseMoses01/playback-mcp (5 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 854 once invoked, about $0.0002 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-31.
Other skills, from other repositories
changelog
Generate a changelog or release notes from Git history, grouped by change type, written in user-facing language, with issue/PR links and breaking changes called out. Conventional-Commits aware and Keep a Changelog formatted; respects any existing CHANGELOG or tooling. Use when preparing release notes or updating…
release-tag
Cut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally signed) Git tag, and pushing the release safely after pre-flight checks. Use when tagging a version, bumping the version, or preparing a release.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.