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 agentmods add rules/symboliclight-agi/governspec/cursor_changeloggit clone --depth 1 https://github.com/SymbolicLight-AGI/GovernSpecWrote 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/symboliclight-agi/governspec/cursor_changelog)<a href="https://agentmods.dev/rules/symboliclight-agi/governspec/cursor_changelog"><img src="https://agentmods.dev/badge/rules/symboliclight-agi/governspec/cursor_changelog.svg" alt="Measured on agentmods" 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.00130 | $0.00130 |
| Opus 5 | $0.00065 | $0.00065 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
cursor_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 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.
What it actually says
Cursor Changelog Rules
Project Goal
Create a concise changelog draft from verified release notes.
Working Constraints
- Do not invent breaking changes.
- Do not claim migration is required without evidence.
Allowed and Forbidden Operations
- Web access: forbidden
- Network access: forbidden
- Filesystem read: allowed
- Filesystem write: forbidden
Output Expectations
- Format: markdown
- Language: en
- Section: Highlights
- Section: Fixes
- Section: Upgrade Notes
Verification
- All sections must be present
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 · 34 lines · 130 tokens per session scan A 8857e8e46bbe
cursor_changelog is a cursor rule published in the GitHub repository SymbolicLight-AGI/GovernSpec (2 stars, last pushed 3mo ago), licensed MIT. It adds 130 tokens to every session, about $0.0006 per session on Opus 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 cursor rules, from other repositories
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.