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/changeloggit clone --depth 1 https://github.com/afaraha8403/balakitWrote 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/afaraha8403/balakit/changelog)<a href="https://agentmods.dev/rules/afaraha8403/balakit/changelog"><img src="https://agentmods.dev/badge/rules/afaraha8403/balakit/changelog.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.00605 | $0.00605 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
changelog 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog maintenance
When to update
Update CHANGELOG.md (at project root) whenever you or the user:
- Add a new feature
- Ship a significant fix (bug fix that affects behavior or correctness)
- Make a notable change (refactor, config, dependency, or UX change worth documenting)
- Remove or deprecate something user-facing
Do not add trivial edits (typos, comment-only, formatting-only) unless the user asks.
Format (grouped by type)
- Unreleased at top. The first section is
## [Unreleased]for changes not yet in a release. - Released versions below. Each release has a section
## [vX.Y.Z]or## [X.Y.Z](e.g.## [v0.0.1-beta.7],## [1.0.0]). Use the exact version string that will be tagged (with or without leadingv). - Newest release first under Unreleased. When you cut a release, the previous
[Unreleased]content can be moved under a new## [vX.Y.Z]section. - Group by type. Within each version section, organize entries under three subsections:
### Features,### Fixes,### Changes. - No type prefix. Items do not need
**Feature:**,**Fix:**, or**Change:**prefixes since they are grouped by section. - One line per item; keep text concise.
Structure:
# Changelog
## [Unreleased]
### Features
- Short description of new feature.
- Another feature.
### Fixes
- Bug fix description.
- Another fix.
### Changes
- Refactor or UX change description.
## [v0.0.1-beta.7]
### Features
- Something shipped in this version.
### Changes
- Another change.
## [v0.0.1-beta.6]
- ...
Releases and GitHub
If the project uses a tag-triggered release workflow, it typically looks in CHANGELOG.md for a section whose heading matches the pushed tag (e.g. ## [v1.2.3] or ## [1.2.3]) and uses that section as the release notes body. Add the version section before tagging so the release notes are populated; if it's missing, the release should still succeed with a default body.
If the file is missing
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.
- 4d ago First seen · 65 lines · 605 tokens per session scan A 417b0b0eaf7a
changelog is a cursor rule published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 7d ago), licensed MIT. It adds 605 tokens to every session, about $0.0030 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.
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
release-ops-demo
Agent rules for release-ops-demo.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.