Borrowing it
Nothing to install: this file belongs to Supermaxman/Homebox-MCP-Server. 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/Supermaxman/Homebox-MCP-Server/main/.claude/commands/update-npm-package.mdgit clone --depth 1 https://github.com/Supermaxman/Homebox-MCP-ServerWrote 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/supermaxman/homebox-mcp-server/update-npm-package)<a href="https://agentmods.dev/commands/supermaxman/homebox-mcp-server/update-npm-package"><img src="https://agentmods.dev/badge/commands/supermaxman/homebox-mcp-server/update-npm-package.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.00000 | $0.00134 |
| Opus 5 | $0.00000 | $0.00067 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
update-npm-package 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 7d 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
Let us update the NPM package to incorporate the latest edits.
Procedure:
1: Iterate package number in package.json.
2: Validate test build.
IF validation is good:
3: Push to registry and push Github.
Note: you'll need an OTP which I will provide. So as soon as you're ready to run npm publish ask me for it.
In commit notes: if you know the update, draft it. If not, I can provide a summary.
Generally: releases will be point releases fixing or tweaking individual tools. Only substantial changes will merit a major version.
Finally:
4: Run update script to update my own copy of the server from the registry.
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.
- 7d ago First seen · 21 lines · 0 tokens per session scan A ff70b605e779
update-npm-package is a command published in the GitHub repository Supermaxman/Homebox-MCP-Server (4 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 134 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).
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.