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/electrikhq/slateWrote 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/electrikhq/slate/changelog-and-tag)<a href="https://agentmods.dev/rules/electrikhq/slate/changelog-and-tag"><img src="https://agentmods.dev/badge/rules/electrikhq/slate/changelog-and-tag/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/electrikhq/slate/changelog-and-tag"><img src="https://agentmods.dev/badge/rules/electrikhq/slate/changelog-and-tag.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.00381 | $0.00381 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
changelog-and-tag 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 10d 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 + tag on ship
Whenever you ship, release, publish, or the user asks to commit a versioned release for electrik/slate:
- Changelog first — update
CHANGELOG.mdbefore the release commit:- Move items out of
## Unreleasedinto a new heading## X.Y.Z[-suffix] - YYYY-MM-DD - Use Keep a Changelog groups:
Added,Changed,Fixed,Deprecated,Removed,Security - Match the version in
composer.json(versionfield)
- Move items out of
- Commit the changelog (and version bump) with the release
- Tag with an annotated tag equal to that version string (prefer
vprefix for stable (v3.0.0); historical alphas may omit it):
git tag -a "X.Y.Z-suffix" -m "Release X.Y.Z-suffix"
git push origin HEAD --tags
- Do not ship a package version bump without both the changelog section and the git tag
- Docs-only or WIP commits may land under
## Unreleasedwithout a tag; creating a tag requires a changelog release section
Examples
- Shipping 3.0.0 →
CHANGELOG.mdhas## [3.0.0] - 2026-…,composer.jsonsays3.0.0, tagv3.0.0 - Bad: push a release commit with no changelog entry
- Bad: create a tag that does not match
composer.json/ changelog heading
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.
- 10d ago First seen · 30 lines · 381 tokens per session scan A 3aac2998ae39
changelog-and-tag is a cursor rule published in the GitHub repository electrikhq/slate (27 stars, last pushed yesterday), licensed MIT. It adds 381 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
wirekit
WireKit component library conventions for AI tooling.
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.