What is shared-memory?

A release workflow for checking a connected code repository, running its available validations, updating project knowledge, committing changes, and pushing them when possible.

Use it to preview or carry out release preparation, create a commit, push changes, and optionally open a pull request for review.

It reduces the chance of releasing from the wrong Git state, skipping checks, or forgetting related project updates.

shared-memory — Cursor rule for Cursor by robotaitai/project-bedrock

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.

Clone the repo

git clone --depth 1 https://github.com/robotaitai/project-bedrock

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/robotaitai/project-bedrock/shared-memory/github.svg)](https://agentmods.dev/rules/robotaitai/project-bedrock/shared-memory)

Your own site

<a href="https://agentmods.dev/rules/robotaitai/project-bedrock/shared-memory"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/shared-memory/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/robotaitai/project-bedrock/shared-memory"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/shared-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 960 This file is loaded in full into every session.

When invoked 960 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original 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.

Model	Per session	Once invoked
Fable 5.1	$0.00960	$0.00960
Opus 5.5	$0.00384	$0.00384
Sonnet 5.5	$0.00192	$0.00192
Haiku 4.5	$0.00096	$0.00096

Measured 1mo ago against content hash 7d9cc9ef06d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

shared-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 1mo 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.

assets/rules/shared-memory.mdc · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Shared Memory

This project stores persistent memory at agent-knowledge/Memory/MEMORY.md. The repo-local ./agent-knowledge path is the working entrypoint and should point to the real dedicated knowledge folder. If Cursor project memory is used, ~/.cursor/projects/<project-id>/memory/ should point to ./agent-knowledge/Memory/ so all agents read and write the same curated files.

When the symlink is missing or broken, create it:

ln -s <workspace>/agent-knowledge/Memory ~/.cursor/projects/<project-id>/memory

Tree structure

Memory is organized as a tree using the same-name branch convention. Agents load only the branches relevant to their current task.

agent-knowledge/
  Memory/
    MEMORY.md               <- root curated-memory index -- always loaded, max ~200 lines
    <topic>.md              <- flat branch note (no subtopics)
    <topic>/
      <topic>.md            <- branch entry note (same name as folder)
      <subtopic>.md         <- leaf note beside the entry
    decisions/
      decisions.md          <- decision log
  Evidence/
    raw/
    imports/

Reading the tree

Memory/MEMORY.md is always loaded automatically. It is a concise index only -- no deep detail.
At session start, identify which branch(es) your task touches from the Branches section.
Read the relevant branch entry notes before starting work.
If the branch has subtopic files needed for your task, read those too.
Do not read branches unrelated to your task -- keep context lean.

Writing to the tree

Memory/MEMORY.md: short branch summaries with relative links. Keep it under 200 lines.
Branch entry note (<topic>.md or <topic>/<topic>.md): stable facts for one focused domain.
Subtopic note (<topic>/<subtopic>.md): created only when a branch note grows beyond ~150 lines.
When adding a subtopic, replace the inline detail in the entry note with a link.
Each note must stay under ~150 lines. Split if bigger.
Link related notes with relative markdown links (e.g., See [perception](perception/perception.md)).
One branch = one functional domain. Do NOT lump unrelated subsystems into one file.

Read the full file on GitHub · 102 lines

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.

1mo ago First seen · 102 lines · 960 tokens per session scan A 7d9cc9ef06d8

Subscribe to this mod's changes

shared-memory is a cursor rule published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 1mo ago), licensed MIT. It adds 960 tokens to every session, about $0.0038 per session on Opus 5.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.

Git and workflow Memory and context Releases

changesets

Changeset format and bump rules enforced by CI.

adobe/spectrum-design-data · 0 tokens

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.

thatrebeccarae/claude-marketing · 50 tokens

shared-memory