Borrowing it
Nothing to install: this file belongs to laf-rge/quickbooks-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/laf-rge/quickbooks-mcp/master/.claude/commands/publish.mdgit clone --depth 1 https://github.com/laf-rge/quickbooks-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/laf-rge/quickbooks-mcp/publish)<a href="https://agentmods.dev/commands/laf-rge/quickbooks-mcp/publish"><img src="https://agentmods.dev/badge/commands/laf-rge/quickbooks-mcp/publish/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/laf-rge/quickbooks-mcp/publish"><img src="https://agentmods.dev/badge/commands/laf-rge/quickbooks-mcp/publish.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.00716 |
| Opus 5 | $0.00000 | $0.00358 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
publish 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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a new version of quickbooks-mcp to npm and the MCP Registry.
Arguments
$ARGUMENTS should be the version bump type: patch, minor, or major.
If no argument is provided, ask the user which bump type they want (patch, minor, or major) before proceeding.
Steps
1. Pre-flight checks
- Verify the working directory is clean (
git statusshows no uncommitted changes). If there are uncommitted changes, stop and ask the user to commit or stash them first. - Verify
npm whoamisucceeds (user is logged into npm). - Start from an up-to-date master and branch off it — this repo never commits directly to
master, releases included:git fetch origin && git switch -c chore/release-{new_version} origin/master
2. Version bump
- Read the current version from
package.json. - Compute the new version based on the bump type argument (patch/minor/major) using semver rules.
- Update the
versionfield inpackage.json. - Update both the top-level
versionandpackages[0].versionfields inserver.jsonto match. - Show the user: "Bumping version: {old} -> {new}" and confirm before proceeding.
3. Build verification
- Run
npm run buildand verify it completes without errors. - If the build fails, stop and show the errors. Do not proceed with publishing.
4. Open the release PR
The version bump lands on master through review like any other change.
- Stage
package.json,package-lock.json, andserver.json. - Commit with message:
v{new_version} - Push the branch and open a PR titled
v{new_version}summarizing what ships in the release. - Stop here and wait for the user to merge. Do not merge it yourself.
5. Publish to npm
Only proceed after the release PR is merged. Switch back to master and pull first, so the published artifact matches the merged tree:
git switch master && git fetch origin && git pull
npm publish requires passkey authentication via browser. Do NOT run npm publish
directly — it will fail waiting for interactive auth.
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.
- 10d ago First seen · 83 lines · 0 tokens per session scan A d2f63fc3acf4
publish is a command published in the GitHub repository laf-rge/quickbooks-mcp (13 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 716 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
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.
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.
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.