centralaizer-memory

centralaizer-memory is a cursor rule for Cursor from lestercoyoyjr/Centralaizer-public. It costs 197 tokens per session, scanned A, original, no licence file.

A shared-memory rule for Centralaizer, a hub that stores information for agents to reuse across sessions.

In plain words
What is it for?
Use it to guide how shared memory is read and updated during agent work.
Why use it?
It tells the agent to recall relevant information before working and save useful information afterward.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/lestercoyoyjr/centralaizer-public/centralaizer-memory
Clone the repo
git clone --depth 1 https://github.com/lestercoyoyjr/Centralaizer-public

Made for: Cursor.

Wrote 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.

agentmods badge for centralaizer-memory

README.md
[![agentmods](https://agentmods.dev/badge/rules/lestercoyoyjr/centralaizer-public/centralaizer-memory.svg)](https://agentmods.dev/rules/lestercoyoyjr/centralaizer-public/centralaizer-memory)
Your own site
<a href="https://agentmods.dev/rules/lestercoyoyjr/centralaizer-public/centralaizer-memory"><img src="https://agentmods.dev/badge/rules/lestercoyoyjr/centralaizer-public/centralaizer-memory.svg" alt="Measured on agentmods" height="20"></a>
Per session 197 This file is loaded in full into every session.
When invoked 197 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00197 $0.00197
Opus 5 $0.00098 $0.00098
Sonnet 5 $0.00039 $0.00039
Haiku 4.5 $0.00020 $0.00020

Measured 5d ago against content hash e28365a9a79c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

centralaizer-memory 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 5d 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.

.cursor/rules/centralaizer-memory.mdc · 16 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 5d ago First seen · 16 lines · 197 tokens per session scan A e28365a9a79c

Subscribe to this mod's changes

centralaizer-memory is a cursor rule published in the GitHub repository lestercoyoyjr/Centralaizer-public (3 stars, last pushed 10d ago), with no licence file. It adds 197 tokens to every session, about $0.0010 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.