Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ameenmari/agentprodreadyWrote 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/rules/ameenmari/agentprodready/versioning-and-npm-distribution)<a href="https://agentmods.dev/rules/ameenmari/agentprodready/versioning-and-npm-distribution"><img src="https://agentmods.dev/badge/rules/ameenmari/agentprodready/versioning-and-npm-distribution/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/rules/ameenmari/agentprodready/versioning-and-npm-distribution"><img src="https://agentmods.dev/badge/rules/ameenmari/agentprodready/versioning-and-npm-distribution.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.00449 | $0.00449 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
versioning-and-npm-distribution 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 8d 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
Versioning & npm Distribution
Keep versions intact
- Do not mechanically bump every
@agentprodready/*package. - Bump a package version only when its production source or public surface actually changes.
- Root
package.jsonprivate monorepo version is independent of public package versions. @agentprodready/platform-hoststaysprivate: true(never publish to npm).- Git tags use
vMAJOR.MINOR.PATCHfor product releases that ship public package bumps (example:v1.1.0when agent-framework becomes1.1.0).
Every push (CI)
On every push / pull_request, CI must keep versioning + DX gates green:
pnpm verify-versioning— package version integrity- Standard verify suites in
.github/workflows/ci.yml pnpm test:public-dx— packed external install of@agentprodready/agent-framework
Do not publish to npm from ordinary commits.
Release / npm publish flow
- Land code on GitHub (
main) with correct package versions + CHANGELOG. - Create annotated tag
vX.Y.Zwhen cutting a product release. - Publish only packages whose version is not already on npm (prefer
pnpm npm:publishwhich skips already-published versions). - Always publish with pnpm (never raw
npm publish) soworkspace:*is rewritten. - Optional GitHub Actions:
.github/workflows/release.ymlonv*tags; npm job remains gated bypublish_npm/NPM_TOKEN.
Agent rules when releasing
- Commit and push only when the user asks to deploy/publish.
- Never commit secrets,
.env, orpnpm-publish-summary.jsontokens. - After npm publish, verify with
npm view @agentprodready/<pkg> version. - Document selective bumps in CHANGELOG (which packages moved, which stayed).
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.
- 8d ago First seen · 40 lines · 449 tokens per session scan A 23a21b3da4d2
versioning-and-npm-distribution is a cursor rule published in the GitHub repository ameenmari/agentprodready (5 stars, last pushed 26d ago), licensed MIT. It adds 449 tokens to every session, about $0.0022 per session on Opus 5. 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 cursor rules, from other repositories
semver-changelog-agent
Apply when versioning software releases, maintaining changelogs, or setting up automated release processes (like semantic-release). Enforces strict Semantic Versioning (MAJOR.MINOR.PATCH), maintaining a clear CHANGELOG.md (e.g., Keep a Changelog format), and potentially using conventional commits for automation.…
git-author
Git author identity for commits so GitHub attributes contributions correctly.
nauro-ship-task
Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.