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/steipete/agent-rulesWrote 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/steipete/agent-rules/add-to-changelog)<a href="https://agentmods.dev/rules/steipete/agent-rules/add-to-changelog"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/add-to-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/steipete/agent-rules/add-to-changelog"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/add-to-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.00260 | $0.00260 |
| Opus 5.5 | $0.00104 | $0.00104 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
add-to-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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-to-changelog — 100% identical, 0 lines differ
What it actually says
Add to Changelog
Update the project's CHANGELOG.md file with a new entry.
Usage:
/add-to-changelog <version> <change_type> <message>
Parameters:
<version>: Version number (e.g., "1.1.0")<change_type>: One of: "added", "changed", "deprecated", "removed", "fixed", "security"<message>: Description of the change
Examples:
/add-to-changelog 1.1.0 added "New markdown to BlockDoc conversion feature"/add-to-changelog 1.0.2 fixed "Bug in HTML renderer causing incorrect output"
Steps:
- Check for existing CHANGELOG.md or create if missing
- Find or create section for the specified version
- Add the new entry under the appropriate change type
- Format according to Keep a Changelog conventions
- Write the updated changelog back to file
- Optionally commit the changes with appropriate message
Format:
Follow Keep a Changelog format:
- Group changes by type
- List changes as bullet points
- Include date for version sections
- Keep entries concise but descriptive
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.
- 1mo ago First seen · 30 lines · 260 tokens per session scan A 6f2b6a7ba8a5
add-to-changelog is a cursor rule published in the GitHub repository steipete/agent-rules (5,675 stars, last pushed 5mo ago), licensed MIT. It adds 260 tokens to every session, about $0.0010 per session on Opus 5.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
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
zip-contents-protection.crux
⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.
version-bump.crux
⟦CRUX:version-bump.md Κ{M=X.0.0;m=0.X.0;p=0.0.X} R{fix|docs|style|refactor|perf|test|chore→p;feat→m;BREAKING|!→M} Λ{⊲commit→Δ.crux/crux.json»stage} P{1bump;↑→↓0;¬conv→?} ⟧.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.