Borrowing it
Nothing to install: this file belongs to SiroSuzume/mcp-ts-morph. 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/SiroSuzume/mcp-ts-morph/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/SiroSuzume/mcp-ts-morphWrote 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/sirosuzume/mcp-ts-morph/release)<a href="https://agentmods.dev/skills/sirosuzume/mcp-ts-morph/release"><img src="https://agentmods.dev/badge/skills/sirosuzume/mcp-ts-morph/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.00069 | $0.00898 |
| Opus 5 | $0.00034 | $0.00449 |
| Sonnet 5 | $0.00014 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new version
This package publishes to npm via tag-triggered GitHub Actions.
Git tag is the single source of truth for the version — there is no
package.json bump step. release.yml reads the tag, bakes the value into
src/version.ts and package.json, then pnpm publishs with provenance.
Pre-flight checks
- Confirm we are on
mainand clean:git checkout main && git pull --ff-only git status --short # must be empty - Confirm the last CI run on main is green (recent merge passed checks).
- Decide the new version. Default rule:
feat:commit since last tag → minor bump (1.X.0)fix:only → patch bump (1.0.X)- Breaking change → major bump (X.0.0)
- When in doubt, ask the user.
- Stable SemVer only. Prerelease tags (
v1.2.0-rc.1), build metadata (v1.2.0+build.5), and leading zeros (v01.02.03) are rejected by both the workflow trigger andscripts/release-version.mjs. If a prerelease channel is needed, update the workflow glob, the script's STRICT_SEMVER, and this skill together.
- Verify the planned tag does not already exist:
git tag --list 'v*' | sort -V | tail -5
Steps
-
Confirm the target version with the user if they did not specify it explicitly.
-
Create and push the tag:
git tag vX.Y.Z git push origin vX.Y.Z -
Watch the release workflow until it finishes:
gh run list -R SiroSuzume/mcp-ts-morph --workflow=release.yml --limit 1 gh run watch <id> --exit-statusThe workflow performs in order:
- Install dependencies
- Resolve version from tag ref (strict SemVer, no prerelease)
pnpm test(run against the placeholder0.0.0-development)- Bake VERSION into
src/version.tsandpackage.jsonvianode scripts/release-version.mjs --bake <version> pnpm build- Verify
dist/version.jscontains the exact baked line - Strip internal
_version_notefrompackage.json pnpm publish --provenancevia npm Trusted Publishing (OIDC)
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.
- 8d ago First seen · 85 lines · 69 tokens per session scan A 3c33ac66967a
release is a skill published in the GitHub repository SiroSuzume/mcp-ts-morph (16 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 898 once invoked, about $0.0003 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 skills, from other repositories
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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.