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/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/change-tracker)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/change-tracker"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/change-tracker/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/gktuoktay/ai-skills/change-tracker"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/change-tracker.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.00626 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
change-tracker 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Tracker & Versioning Standard
This skill mandates that every meaningful code change (feature, bugfix, refactor) in the project is immediately documented and that the version history (changelog) is kept in a standard format.
📌 Core Rules
- Continuous Tracking: When a task or module is completed in the code, immediately add the changes to
CHANGELOG.md(or the relevant Markdown document in the project structure) rather than keeping them in mind. - Standard Format: Log changes in accordance with the "Keep a Changelog" (keepachangelog.com) standard.
- Versioning: Adhere to Semantic Versioning (SemVer) rules (MAJOR.MINOR.PATCH).
- Unreleased Management: Always group in-development changes under the
[Unreleased](or current sprint/target version) heading.
📝 Format Template
Use the following structure in the CHANGELOG.md file (or similar version tracking file):
# Changelog
All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New UI components for the user login screen.
- New indexing structure for database optimization.
### Changed
- Authentication service updated to use OAuth2.
### Fixed
- Fixed the horizontal scrolling issue on mobile view.
## [1.0.2] - 2026-08-10
### Fixed
- Fixed the 500 error returned when the API rate limit is exceeded (changed to 429).
🔄 Workflow
- Code Development: Write or modify the code as requested.
- Log Update: Add a clean bullet point summarizing the work done under the
[Unreleased]heading (or appropriate version) in the relevant category (Added, Changed, Fixed, Removed, etc.) in theCHANGELOG.mdfile. - Pre-Commit Check: Right before committing changes with
git-conventional-commits, ensure that theCHANGELOG.mdfile is saved.
🛠 Categories to Use
- Added: for new features.
- Changed: for changes in existing functionality.
- Deprecated: for soon-to-be removed features.
- Removed: for now removed features.
- Fixed: for any bug fixes.
- Security: in case of vulnerabilities.
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.
- 6d ago First seen · 56 lines · 626 tokens per session scan A 29749f4373e0
change-tracker is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 626 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-09-03.
Other cursor rules, from other repositories
commit
Quality gate runs FIRST. Do NOT commit if any gate fails. Do NOT ask for permission or skip the gate.
commit-authorship
Git commits must be authored by the user only (no Cursor co-author).
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.