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/afaraha8403/balakit/releasegit clone --depth 1 https://github.com/afaraha8403/balakitWhat 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.00564 | $0.00564 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
release 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 2d 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 version lockstep
One version. The git tag, package.json "version", CHANGELOG heading, and npm publish are the same semver. Never tag or publish a version that is not already committed in package.json.
Identity
| Surface | Form | Example |
|---|---|---|
package.json "version" |
no leading v |
1.14.0 or 1.15.0-beta.1 |
| git tag | v + that string |
v1.14.0 or v1.15.0-beta.1 |
| CHANGELOG heading | ## [vX.Y.Z] (or without v) |
## [v1.14.0] |
| npm | that same package.json version |
[email protected] (latest) or dist-tag beta |
Plugin / marketplace version fields lockstep with package.json. Skill SKILL.md version: does not. Bump package.json only, then ./sync.sh. Never hand-edit generated plugin versions.
Order
- Cut CHANGELOG
[Unreleased]into## [vX.Y.Z]. - Set
package.json"version"toX.Y.Z(nov). ./sync.shthennpm testandnode scripts/check-lockstep.mjs --rebuild --git.- Commit. Tag that commit:
git tag -a vX.Y.Z -m "vX.Y.Z". - Push the tag only after the commit is on the release branch. The
v*workflow creates the GitHub Release and runsnpm publish. Do not alsogh release createornpm publishlocally — that duplicates the tag and can publish a different version than the tag.
If the tag workflow fails after the GitHub Release exists, do not publish a different version locally to "catch up." Fix the secret/token, then re-run the same tag job (make gh release create a no-op if the release already exists).
npm auth
GitHub Actions NPM_TOKEN must be an npm Automation token (bypasses 2FA). Publish/classic tokens fail CI with EOTP.
Procedure: release-deploy skill + skills/release-deploy/projects/<owner>-<repo>.md.
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.
- 2d ago First seen · 36 lines · 564 tokens per session scan A c3b4db1cc911
release is a cursor rule published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 4d ago), licensed MIT. It adds 564 tokens to every session, about $0.0028 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
github
GitHub repository operations: PRs, issues, releases, branch protection, CODEOWNERS, Dependabot, and repo settings audits. Use when user says 'review my PR', 'create a release', 'cut a release', 'tag a release', 'set up branch protection', 'add CODEOWNERS', 'audit repo settings', 'is Dependabot configured', or asks…
ui
React components must be functional and prop-typed.
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
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.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.