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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/changesets)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/changesets"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/changesets/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/louisbrulenaudet/monorepo-template/changesets"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/changesets.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.01418 |
| Opus 5.5 | $0.00000 | $0.00567 |
| Sonnet 5.5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
changesets 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 15d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changesets
A changeset is the release note for one user-visible change. Its readers operate or call the deployed apps, in apps/<app>/CHANGELOG.md and in the GitHub Release CD builds from those files; rationale and implementation go in the commit and PR body. Procedure: skill changeset. Config, gate, and pipeline internals: release.mdc.
When
pnpm release:check decides whether a shipped path changed. It also runs in pnpm run ci and PR CI. Every file of an app or of a package it bundles counts, except tests, top-level *.md, turbo.json, Vitest config, and @repo/vitest-config.
| Change | Changeset |
|---|---|
Observable change to a deployed app, including through a bundled @repo/* package |
patch or minor (see Bump) |
Catalog bump of an entry an app lists under dependencies |
patch naming that app; Dependabot PRs get one committed for them when CHANGESET_BOT_TOKEN is set |
Shipped path changed, nothing observable: types, comments, a behavior-identical refactor, devDependency lines in an app package.json |
--empty with a one-line reason; changeset version deletes it unread |
Tests, docs, .github/, agent config, or root tooling only |
none |
- A fix to a change still pending on
mainedits that pending changeset: nothing has shipped, so there is nothing new to note. - One changeset per logical change: a fix and a feature in one PR are two files. Iterating on your own PR edits the file you added, never a second one for the same change.
Frontmatter
- Name only apps - the unscoped workspaces under
apps/- each one whose behavior changes. Never an@repo/*package: its entry lands in apackages/*/CHANGELOG.mdthat no release note reads.release:checkenforces this. - The
fixedgroup bumps every app to the highest bump anyway; the names only decide which CHANGELOG carries the entry. An app no changeset names gets "No changes in this release.", which the GitHub Release skips.
Bump
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.
- 15d ago First seen · 66 lines · 0 tokens per session scan A c644c2b39a88
changesets is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,418 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-10-01.
Other cursor rules, from other repositories
mcp-releasing
Steps and procedures for releasing MCP (Model Context Protocol) servers as NPM packages.
add-to-changelog
Update the project's CHANGELOG.md file with a new entry.
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.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
release-git-tags-auto
This rule checks for existing tags before creating new ones. It also offers to push the tag to the remote repository. It runs when users request release creation, version bumping, or package publishing.
release-changelog-auto
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.