Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/georgekhananaev/claude-skills-vaultnpx agentmods add commands/georgekhananaev/claude-skills-vault/git-npm-releaseWrote 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/commands/georgekhananaev/claude-skills-vault/git-npm-release)<a href="https://agentmods.dev/commands/georgekhananaev/claude-skills-vault/git-npm-release"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/git-npm-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/commands/georgekhananaev/claude-skills-vault/git-npm-release"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/git-npm-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.00000 | $0.00946 |
| Opus 5 | $0.00000 | $0.00473 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
git-npm-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 11d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Command
IMPORTANT: This command ONLY runs when explicitly invoked via /git-npm-release. Do NOT auto-release.
Goal: Create a versioned release — bump CHANGELOG, regenerate manifest, commit, push, tag, and trigger npm publish via GitHub Actions.
1. Pre-Release Checks
Step 1: Clean Working Tree
git status --porcelain
If uncommitted changes exist:
- Ask user: "You have uncommitted changes. Run /git-commit first?"
- If NO: Abort
Step 2: Check Unreleased Content
- Read
CHANGELOG.md→ check if## [Unreleased]section has content - If empty: Inform user "Nothing to release — Unreleased section is empty" → Exit
2. Version Selection
Use AskUserQuestion to prompt:
Question: "Which version bump?"
Options:
- Patch (+0.0.1) - Bug fixes, minor updates (Recommended)
- Minor (+0.1.0) - New features, backwards compatible
- Major (+1.0.0) - Breaking changes
Calculate new version from latest ## [X.X.X] entry in CHANGELOG.
3. Update Files
Step 1: Update CHANGELOG.md
- Move
## [Unreleased]content into new## [X.X.X] - YYYY-MM-DDsection - Create fresh empty
## [Unreleased]above it
Step 2: Regenerate All Auto-Generated Files
node scripts/generate-manifest.js
node scripts/generate-docs.js
node scripts/generate-notice.js
This updates:
manifest.json+cli/manifest.json— skill/command/mcp indexSKILLS.md— skill table with install commandsCOMMANDS.md— command table with invocationscli/README.md— npm package README with current countsNOTICE— credits and attribution
Step 3: Update CLI package version
cd cli && npm version X.X.X --no-git-tag-version --allow-same-version
Step 4: Commit
git add CHANGELOG.md manifest.json cli/manifest.json cli/package.json cli/README.md SKILLS.md COMMANDS.md NOTICE
git commit -m "chore(release): bump version to X.X.X"
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.
- 11d ago First seen · 116 lines · 0 tokens per session scan A 70dc2a6c1ff3
git-npm-release is a command published in the GitHub repository georgekhananaev/claude-skills-vault (28 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 946 tokens. 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 commands, from other repositories
gh-release
Create a new GitHub release by triggering the Release workflow.
gh-retry
Rerun all failed and cancelled workflow runs for a GitHub PR or all my PRs in a repo.
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
quick-commit
Quick commit with automatic formatting, linting, and conventional commit message.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.