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.
npx agentmods add rules/sthamann/nyx-local-ai/release-versioninggit clone --depth 1 https://github.com/sthamann/nyx-local-aiWrote 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/sthamann/nyx-local-ai/release-versioning)<a href="https://agentmods.dev/rules/sthamann/nyx-local-ai/release-versioning"><img src="https://agentmods.dev/badge/rules/sthamann/nyx-local-ai/release-versioning.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 | $0.00426 | $0.00426 |
| Opus 5 | $0.00213 | $0.00213 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
release-versioning 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 5d 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 & versioning
The repo slug is sthamann/nyx-local-ai — it appears in install.sh,
install.ps1, README and package.json (scripts.package baseImagesUrl).
Never introduce a different slug.
Version bump checklist (all three, always together)
package.json→"version"README.md→ status line (**vX.Y.Z**) and everynyx-local-ai-X.Y.Z.vsixmentionsrc/mcp/client.ts→clientInfo.version
Quality gates before packaging
Run in this order; all must pass:
npm run typecheck
node .harness/smoke.mjs # parser/edit logic — must print ALL PASS
node .harness/readme-check.mjs # README/version sync — must print ALL PASS
npm run build
npm run package
The readme-check also catches missed version bumps (it verifies all three
locations), so don't rely on sed output alone — seds fail silently.
Releasing
Releases are produced only by CI (.github/workflows/release.yml):
git tag vX.Y.Z && git push origin vX.Y.Z builds and attaches
nyx-local-ai.vsix + checksums.txt — the exact artifact names
install.sh/install.ps1 download and verify. Never hand-upload artifacts.
VSIX size
The package must stay ≈4–6 MB. node_modules ships in the VSIX (tesseract.js
is external), so when adding a runtime dependency, extend .vscodeignore to
strip its dead weight and check the size vsce reports after npm run package.
Dev-only dependencies (bundled by esbuild, e.g. marked, highlight.js)
belong in devDependencies.
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.
- 5d ago First seen · 47 lines · 426 tokens per session scan A 6f35d7d05a77
release-versioning is a cursor rule published in the GitHub repository sthamann/nyx-local-ai (137 stars, last pushed 1mo ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 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-30.
Other cursor rules, from other repositories
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
release-policy
Release, versioning, and signing policy for setmac.
new-user-experience-nux-flow-rule
Details the new user experience flow, guiding users through the initial setup and configuration.
bump-project-version
The user can provide version in one of three ways.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.