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/Pranav-Karra-3301/tuckWrote 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/pranav-karra-3301/tuck/changelog)<a href="https://agentmods.dev/rules/pranav-karra-3301/tuck/changelog"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/changelog/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/pranav-karra-3301/tuck/changelog"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/changelog.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.00000 | $0.00511 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Rules
Automatic Generation
CHANGELOG.md is automatically generated by semantic-release based on commit messages.
How It Works
- Commits to
maintrigger release workflow - semantic-release analyzes commit messages
- Version is determined by commit types
- CHANGELOG.md is updated automatically
- npm package is published
- GitHub release is created
Commit Message Impact
| Commit Type | Version Bump | Changelog Section |
|---|---|---|
feat: |
Minor (0.x.0) | Features |
fix: |
Patch (0.0.x) | Bug Fixes |
perf: |
Patch (0.0.x) | Performance |
BREAKING CHANGE |
Major (x.0.0) | Breaking Changes |
docs: |
None | Not included |
style: |
None | Not included |
refactor: |
None | Not included |
test: |
None | Not included |
chore: |
None | Not included |
Writing Good Commit Messages
For meaningful changelog entries:
# Good - describes user-facing change
feat: add restore command for backup recovery
fix: prevent data loss when sync fails mid-operation
# Bad - too vague
feat: add new feature
fix: fix bug
Breaking Changes
Mark breaking changes clearly:
feat!: redesign configuration file format
BREAKING CHANGE: The config.json format has changed.
Users must migrate their configuration files using
the new 'tuck config migrate' command.
Manual Changelog Edits
NEVER manually edit CHANGELOG.md:
- It will be overwritten by semantic-release
- Use commit messages to control content
- Use conventional commits format
Release Notes
GitHub releases are created automatically with:
- Version number from package.json
- Changelog entries for this version
- Links to commits and PRs
- Binary artifacts attached
Changelog Format
The generated changelog follows Keep a Changelog format:
# Changelog
## [1.2.0] - 2024-01-15
### Features
* add restore command for backup recovery (abc1234)
### Bug Fixes
* prevent data loss when sync fails (def5678)
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.
- 9d ago First seen · 93 lines · 0 tokens per session scan A 1cb695a71d68
changelog is a cursor rule published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 511 tokens. 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
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.…
hatch3r-git-conventions
Conventional Commits type list, subject line rules, breaking-change footer format, branch naming template for type/short-description, and change-size discipline (PR-size ceiling with stacked-change escape hatch).
release-discipline
Release batching, gitignore policy, and pre-tag checks.
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.
release-checklist
What to update with each code change or version release.