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 skills add usrrname/cursorrules --skill changeloggit clone --depth 1 https://github.com/usrrname/cursorrulesWrote 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/skills/usrrname/cursorrules/changelog)<a href="https://agentmods.dev/skills/usrrname/cursorrules/changelog"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/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/skills/usrrname/cursorrules/changelog"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/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.00009 | $0.00472 |
| Opus 5.5 | $0.00004 | $0.00189 |
| Sonnet 5.5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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 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.
What it actually says
Changelog Generation Command 📝
Generate a changelog.md by analyzing git history and tags.
Git Commands
# Get all tags sorted by version (newest first)
git tag --sort=-version:refname
# Get the most recent tag
git describe --tags --abbrev=0
# Get unreleased commits since last tag
git log --oneline --no-merges $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD
# Get commits between two tags
git log --oneline --no-merges <prev-tag>..<current-tag>
# Get tag creation date
git log -1 --format=%ai <tag-name>
Loop Through All Tags
ALL_TAGS=$(git tag --sort=-version:refname)
for tag in $ALL_TAGS; do
PREV_TAG=$(git describe --tags --abbrev=0 $tag^ 2>/dev/null || echo "")
COMMITS=$(git log --oneline --no-merges $PREV_TAG..$tag)
echo "Version $tag:"
echo "$COMMITS"
echo "---"
done
Filter by Conventional Commit Type
# Features
git log --oneline --grep="^feat:" <tag1>..<tag2>
# Bug fixes
git log --oneline --grep="^fix:" <tag1>..<tag2>
# Documentation
git log --oneline --grep="^docs:" <tag1>..<tag2>
# Breaking changes
git log --oneline --grep="BREAKING" <tag1>..<tag2>
Generate Changelog
Run these commands and format output following Keep a Changelog format:
- Analyze all git tags
- Categorize commits by type (feat, fix, docs, chore, etc.)
- Create sections: Added, Fixed, Changed, Documentation
- Include unreleased changes at the top
- Store at project root as
changelog.md
See .cursor/rules/utils/changelog-generator-manual.mdc for full formatting rules.
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 · 71 lines · 9 tokens per session scan A e96497a7530e
changelog is a skill published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 9 tokens to every session and 472 once invoked, about $0.0000 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-31.
Other skills, from other repositories
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
changeset
USE WHEN: a change under apps/ or packages/ (or an app runtime dependency bump) needs its release note, the user asks to add, fix, or check a changeset, a PR is about to open, or pnpm release:check fails. DO NOT USE WHEN: editing the release pipeline itself (.changeset/config.json, release.yml, the check scripts) …
deploy-npm
Release an npm package: version, CHANGELOG, publish, verify. Use when "publish this package", "release to npm", or "ship a new npm version". Running-app production deploy → workflow-ship-and-observe.
bumpup-versions
Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number.
manage-changelog
Manage changelogs using Changie. Provides tools to initialize, add change fragments, batch releases, and merge version notes. Requires 'changie' to be installed.
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.