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/drumnation/unsplash-smart-mcp-serverWrote 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/drumnation/unsplash-smart-mcp-server/changelog.rules)<a href="https://agentmods.dev/rules/drumnation/unsplash-smart-mcp-server/changelog.rules"><img src="https://agentmods.dev/badge/rules/drumnation/unsplash-smart-mcp-server/changelog.rules.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.00907 | $0.00907 |
| Opus 5 | $0.00453 | $0.00453 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
changelog.rules 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Management Rules
Changelog Purpose & Standards
This file provides rules for managing changelog files within the project-brain-monorepo.
Format Standards
- All changelogs MUST follow Keep a Changelog format
- Version numbers MUST adhere to Semantic Versioning
- Each package MUST maintain its own CHANGELOG.md in its root directory
Required Structure
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](mdc:https:/keepachangelog.com/en/1.0.0),
and this project adheres to [Semantic Versioning](mdc:https:/semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New features
### Changed
- Changes to existing functionality
### Deprecated
- Soon-to-be removed features
### Removed
- Removed features
### Fixed
- Bug fixes
### Security
- Vulnerability fixes
## [x.y.z] - YYYY-MM-DD
Change Categories
- Added - New features
- Changed - Changes to existing functionality
- Deprecated - Soon-to-be removed features
- Removed - Removed features
- Fixed - Bug fixes
- Security - Vulnerability fixes
Workflow Rules
Adding New Changes
- ✅ ALWAYS add changes to the [Unreleased] section first
- ✅ ALWAYS include a concise description of the change
- ✅ ALWAYS categorize changes correctly
- ⛔ NEVER add the same change multiple times
- ✅ ALWAYS maintain chronological order within each category (newest at top)
Release Process
- ✅ ALWAYS get the current date using terminal command:
date +'%Y-%m-%d' - ✅ ALWAYS move [Unreleased] content to a new version section with the date
- ✅ ALWAYS create an empty [Unreleased] section after a release
- ✅ ALWAYS include links to compare versions (at bottom of file)
- ✅ ALWAYS update the version in package.json to match the new release version
Version Management
Package.json Synchronization
- ✅ ALWAYS update package.json version when creating a new release
- ✅ ALWAYS ensure package.json version and CHANGELOG.md version match exactly
- ⛔ NEVER have mismatched versions between package.json and CHANGELOG.md
- ✅ ALWAYS update both files in the same commit
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.
- 8d ago First seen · 119 lines · 907 tokens per session scan A a85ac77a0a26
changelog.rules is a cursor rule published in the GitHub repository drumnation/unsplash-smart-mcp-server (63 stars, last pushed 7mo ago), licensed MIT. It adds 907 tokens to every session, about $0.0045 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
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.