Borrowing it
Nothing to install: this file belongs to samson-art/transcriptor-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/samson-art/transcriptor-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/samson-art/transcriptor-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/samson-art/transcriptor-mcp/release)<a href="https://agentmods.dev/skills/samson-art/transcriptor-mcp/release"><img src="https://agentmods.dev/badge/skills/samson-art/transcriptor-mcp/release/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/skills/samson-art/transcriptor-mcp/release"><img src="https://agentmods.dev/badge/skills/samson-art/transcriptor-mcp/release.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.00055 | $0.01354 |
| Opus 5.5 | $0.00022 | $0.00542 |
| Sonnet 5.5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00135 |
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 16d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
A tag push deploys production. CI publishes :X.Y.Z and :latest. Then the hosted deployment pulls :latest on its own.
Before each step that merges, tags or pushes, get an explicit go-ahead from the maintainer in this session.
Only a PR that changes shipped behavior is a release. Docs, legal and chore PRs merge without a version.
1. In the PR, before merge
- Version: Set X.Y.Z to the next version after the newest tag (
git tag --sort=-v:refname | head -1). Never set a lower version. The number in the branch name is only a guess. The tag decides. - Bump the version in four places:
package.jsonversionpackage-lock.json(the two top-level version fields)server.jsonversionserver.jsonpackages[0].identifier(the image tag)
- CHANGELOG: Write it with the
simple-englishskill.- Move the entries into
## [X.Y.Z] - YYYY-MM-DD. The date is the tag date. If the tag slips a day, correct the date. - Keep
## [Unreleased]empty at the top. - Use Keep a Changelog subsections (Added, Changed, Fixed, Security). Start each entry with a short sentence that says what changed, without bold. Write it for operators and callers, and give the measured numbers.
- Name new, changed or removed env vars. Each of them must also be in
.env.example. If operators set them, they must also be in the README env table.
- Move the entries into
- PR title and body: The title is
X.Y.Z: <one sentence>. In the body, add an After merge section. It lists the post-deploy checks that show that the change works. - Ready to merge: A PR is ready to merge with these three conditions:
- The gate is green on the last commit.
- Every review fix is pushed.
- The PR is out of draft.
2. Merge and check ancestry
- The maintainer merges with a merge commit, not a squash. If the maintainer asks you to merge, use
gh pr merge N --merge. - Pull the merge commit:
git switch main git pull --ff-only - Prove that the merge contains the whole PR. This includes fixes that someone pushed after a click on Merge:
Never read "already merged" as "merged with my latest push". If a commit is missing, open a follow-up PR and release that PR instead. In Claude Code, thegh pr view N --json headRefOid,headRefName git merge-base --is-ancestor <headRefOid> <merge sha> git merge-base --is-ancestor origin/<headRefName> <merge sha> # if the branch still existsguard-releasehook does this check again at tag time.
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.
- 16d ago Changed 8ea2c3b1eb24
- 21d ago First seen · 81 lines · 55 tokens per session scan A b0d1d5ca9b6e
release is a skill published in the GitHub repository samson-art/transcriptor-mcp (23 stars, last pushed 10d ago), licensed MIT. It adds 55 tokens to every session and 1,354 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
oma-dev-workflow
Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.