Borrowing it
Nothing to install: this file belongs to yyordanov-tradu/stock-scanner-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/yyordanov-tradu/stock-scanner-mcp/main/.claude/commands/release-npm.mdgit clone --depth 1 https://github.com/yyordanov-tradu/stock-scanner-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/commands/yyordanov-tradu/stock-scanner-mcp/release-npm)<a href="https://agentmods.dev/commands/yyordanov-tradu/stock-scanner-mcp/release-npm"><img src="https://agentmods.dev/badge/commands/yyordanov-tradu/stock-scanner-mcp/release-npm/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/yyordanov-tradu/stock-scanner-mcp/release-npm"><img src="https://agentmods.dev/badge/commands/yyordanov-tradu/stock-scanner-mcp/release-npm.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.00511 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
release-npm 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.
What it actually says
Release a new version to npm. Argument: version bump type ($ARGUMENTS — one of: patch, minor, major). Defaults to "patch" if not specified.
Steps
-
Pre-flight checks
- Check current branch — if NOT on
main, automatically switch:git checkout main - Ensure working tree is clean (no uncommitted changes). Untracked files are OK.
- Sync with remote:
git pullto get latest - Verify local
mainmatchesorigin/main(no unpushed commits) - Run quality gates:
npm run lint && npm test && npm run build - Stop and report if anything fails
- Check current branch — if NOT on
-
Bump version
- Run
npm version $ARGUMENTS --no-git-tag-version(default: patch) - Read the new version from package.json
- Run
-
Update version references across the project
- Update
CLAUDE.mdversion string (e.g.**Version:** X.Y.Z) - Update
README.mdif it contains a hardcoded version reference - Update
.claude-plugin/plugin.jsonversionto matchpackage.json— the Claude Code plugin manifest carries its own copy.npm versiondoes not touch it, so it must be bumped here in lockstep.src/__tests__/plugin-manifests.test.tsfails CI if they drift, but updating both in the same commit avoids a red test mid-release. - Verify module/tool counts in
README.mdandCLAUDE.mdstill match reality
- Update
-
Create release branch, commit, tag
git checkout -b release/v<version>git add package.json CLAUDE.md README.md .claude-plugin/plugin.json && git commit -m "chore: release v<version>"git tag -a v<version> -m "v<version>"
-
Push and create PR
git push -u origin release/v<version> && git push origin v<version>- Create PR to main:
gh pr create --title "chore: release v<version>"
-
Merge
- Merge:
gh pr merge --squash --auto git checkout main && git pull- CI/CD will automatically publish to npm when the tag is pushed
- 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.
- 11d ago First seen · 36 lines · 0 tokens per session scan A b28ac7b4dd6e
release-npm is a command published in the GitHub repository yyordanov-tradu/stock-scanner-mcp (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 511 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-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Deploy feature through automated staging validation to production with rollback testing.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.