Borrowing it
Nothing to install: this file belongs to MehrozeKhan73/Business-Central-MCP-Integration. 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/MehrozeKhan73/Business-Central-MCP-Integration/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/MehrozeKhan73/Business-Central-MCP-IntegrationWrote 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/mehrozekhan73/business-central-mcp-integration/release)<a href="https://agentmods.dev/skills/mehrozekhan73/business-central-mcp-integration/release"><img src="https://agentmods.dev/badge/skills/mehrozekhan73/business-central-mcp-integration/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/skills/mehrozekhan73/business-central-mcp-integration/release"><img src="https://agentmods.dev/badge/skills/mehrozekhan73/business-central-mcp-integration/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.00131 | $0.02439 |
| Opus 5 | $0.00066 | $0.01220 |
| Sonnet 5 | $0.00026 | $0.00488 |
| Haiku 4.5 | $0.00013 | $0.00244 |
Grade C, and why
bc-mcp-release scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd .. && rm -rf bc-mcp-smoke This is a copy
100% identical to bc-mcp-release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bc-mcp release runbook
Release business-central-mcp to npm. The package is configured for manual
publish via prepublishOnly (typecheck + build); the rest is gated by you
to keep destructive operations safe.
This is a runbook, not an automated tool. Walk the user through each step, pausing on anything destructive (version bump, publish, tag push) for explicit confirmation. Releases are irreversible — npm allows unpublish only within 72 hours of publish, and only if no other package depends on the exact version.
Preflight checklist
Run these before suggesting a version bump. If any fail, stop and surface the failure — don't paper over it.
cd U:/Git/bc-mcp # or wherever the repo lives
# Working tree clean?
git status --short # expect empty
git rev-parse --abbrev-ref HEAD # expect master
# Up-to-date with origin?
git fetch origin
git status -sb # expect "## master...origin/master" with no behind/ahead
# All tests pass?
npm run typecheck # tsc --noEmit, expect exit 0
npm test # unit + protocol, expect green
npm run test:integration # against live BC, expect green (skip if no BC available, but flag the skip)
# CHANGELOG up-to-date?
grep -q "^## \[Unreleased\]" CHANGELOG.md && echo "OK: [Unreleased] section exists"
# Inspect the [Unreleased] section — it should describe what's about to ship.
If integration tests can't run (no live BC), explicitly tell the user
"integration tests skipped — running CI to compensate". CI will run unit +
protocol on Node 20/22/24 against the master branch via
.github/workflows/ci.yml.
Step 1: Pick the version
Read package.json to see the current version. Compare against published
versions on npm:
npm view business-central-mcp versions --json
Decide the bump per semver:
| Change kind | pre-1.0 (0.x.y) |
post-1.0 (x.y.z) |
|---|---|---|
| Bug fix only | 0.x.y patch |
x.y.z patch |
| New feature, backwards-compatible | 0.x.0 minor |
x.y.0 minor |
| Breaking change to public API | 0.x.0 minor (allowed pre-1.0) |
x.0.0 major |
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 · 254 lines · 131 tokens per session scan C 834f16110737
bc-mcp-release is a skill published in the GitHub repository MehrozeKhan73/Business-Central-MCP-Integration (0 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 2,439 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to bc-mcp-release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.