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/shawnfromportland/agentmemoryforcursorWrote 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/shawnfromportland/agentmemoryforcursor/agent_changelog_management)<a href="https://agentmods.dev/rules/shawnfromportland/agentmemoryforcursor/agent_changelog_management"><img src="https://agentmods.dev/badge/rules/shawnfromportland/agentmemoryforcursor/agent_changelog_management.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.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
agent_changelog_management 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 7d 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
Agent Changelog Management
Purpose of docs/ai/agent_changelog.md
The docs/ai/agent_changelog.md file serves as a record of user-specified operational behaviors, interaction preferences, and custom instructions for the AI assistant. It helps maintain a history of how the AI's behavior has been tailored over time.
Updating the Changelog
Whenever the user makes a request that modifies or defines:
- The AI's behavior (e.g., "respond in a specific tone," "always perform X before Y").
- Operational procedures (e.g., "how to handle commits," "what to do at the start of a session").
- Interaction preferences (e.g., "address me by a specific name," "use a particular format for responses").
The AI assistant MUST:
- run a terminal command to determine today's current date.
- Append a new entry to
docs/ai/agent_changelog.mdunder a heading for the current date. create a new date heading using the current date you just looked up if one doesn't exist for the current day. - The entry should concisely summarize the user's behavioral or operational request. For example:
## YYYY-MM-DD - User requested that [summary of the behavioral/operational request]. - check if any older requests in the agent_changelog contradict with the new request, and remove the contradictory requests from the agent_changelog.
- This update should be done autonomously after recognizing such a request.
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.
- 7d ago First seen · 30 lines · 358 tokens per session scan A a6c365e1f37e
agent_changelog_management is a cursor rule published in the GitHub repository shawnfromportland/agentmemoryforcursor (11 stars, last pushed 1y ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.