Borrowing it
Nothing to install: this file belongs to OleksandrKucherenko/mcp-obsidian-via-rest. 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/OleksandrKucherenko/mcp-obsidian-via-rest/main/.claude/skills/release-it/SKILL.mdgit clone --depth 1 https://github.com/OleksandrKucherenko/mcp-obsidian-via-restWrote 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/oleksandrkucherenko/mcp-obsidian-via-rest/release-it)<a href="https://agentmods.dev/skills/oleksandrkucherenko/mcp-obsidian-via-rest/release-it"><img src="https://agentmods.dev/badge/skills/oleksandrkucherenko/mcp-obsidian-via-rest/release-it/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/oleksandrkucherenko/mcp-obsidian-via-rest/release-it"><img src="https://agentmods.dev/badge/skills/oleksandrkucherenko/mcp-obsidian-via-rest/release-it.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.00123 | $0.01994 |
| Opus 5 | $0.00062 | $0.00997 |
| Sonnet 5 | $0.00025 | $0.00399 |
| Haiku 4.5 | $0.00012 | $0.00199 |
Grade A, and why
release-it 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 12d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release-It Skill
Automate NPM package versioning, changelog generation, and publishing with release-it.
Core Workflow Overview
Setting up release-it involves these steps:
- Install release-it and plugins
- Create configuration file (
.release-it.json) - Configure Git and GitHub settings
- Set up changelog generation (optional but recommended)
- Create GitHub Actions workflow for CI/CD
- Configure authentication (NPM_TOKEN or OIDC)
Step 1: Installation
# Recommended: interactive setup
npm init release-it
# Manual installation
npm install --save-dev release-it
npm install --save-dev @release-it/conventional-changelog # Optional: for changelogs
Add scripts to package.json:
{
"scripts": {
"release": "release-it",
"release:dry": "release-it --dry-run",
"release:ci": "release-it --ci"
}
}
Requirement: Node.js 20 or higher for release-it v19+.
Step 2: Configuration File
Create .release-it.json in project root. See references/config-options.md for all options.
Minimal Configuration
{
"$schema": "https://unpkg.com/release-it@19/schema/release-it.json",
"git": {
"commitMessage": "chore: release v${version}",
"tagName": "v${version}"
},
"github": {
"release": true
},
"npm": {
"publish": true
}
}
Production Configuration (Recommended)
{
"$schema": "https://unpkg.com/release-it@19/schema/release-it.json",
"git": {
"commitMessage": "chore: release v${version}",
"tagName": "v${version}",
"requireBranch": "main",
"requireCleanWorkingDir": true,
"requireCommits": true,
"requireUpstream": true
},
"github": {
"release": true,
"releaseName": "v${version}"
},
"npm": {
"publish": true
},
"hooks": {
"before:init": ["npm run lint", "npm test"],
"after:bump": "npm run build"
},
"plugins": {
"@release-it/conventional-changelog": {
"preset": {
"name": "conventionalcommits",
"types": [
{ "type": "feat", "section": "Features" },
{ "type": "fix", "section": "Bug Fixes" },
{ "type": "perf", "section": "Performance" }
]
},
"infile": "CHANGELOG.md",
"header": "# Changelog"
}
}
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 284 lines · 123 tokens per session scan A 6ee327c423f9
release-it is a skill published in the GitHub repository OleksandrKucherenko/mcp-obsidian-via-rest (13 stars, last pushed 5mo ago), licensed MIT. It adds 123 tokens to every session and 1,994 once invoked, about $0.0006 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-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…