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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/memrain)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/memrain"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/memrain/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/timurgaleev/vibestack/memrain"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/memrain.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.00568 | $0.00568 |
| Opus 5.5 | $0.00227 | $0.00227 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
memrain 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memrain — Persistent Memory
The user's knowledge base is the memrain MCP server. It is the single source of truth for cross-session memory. Do not use any other store (local notes apps, vaults) for assistant memory.
Reading Context
When the user references ongoing projects, decisions, or prior work, query memrain before answering:
- Semantic questions ("what is this product?", "what did I decide about X?")
→ memrain
search/recall - Everything tied to a named project or person →
entity_recall,entity_timeline - Direct page lookup →
page_get, listing →page_list - "What happened recently?" →
chronicle_since,chronicle_day
Grep is still right for known exact strings, regex, and file globs in the current repo.
Code Questions
When the repo is indexed into memrain, ask its code graph before Grep:
- "Where is X defined?" →
code_def - "Who calls X?" →
code_callers; every other use (imports, type uses) →code_refs - "What does this function call?" →
code_calleeswith<path>:<line> - "What breaks if I change X?" →
code_blast; "where does this request end up?" →code_flow
Zero hits means unknown, not absent. An empty result is proof only when its
readiness.state is ready. not_built, indexing or no_symbols — or a
failed call — mean the graph cannot answer: say so, then fall back to Grep.
Never report "nothing calls X" from an empty or failed query.
Saving Information
Save directly to memrain when work produces something worth keeping:
- Discrete facts and decisions →
add_fact - Longer notes, designs, research →
page_put/page_append - Timeline events (shipped X, decided Y) →
add_timeline_event
When to Save
- Architectural or design decisions made during a session
- Discovered constraints, gotchas, or non-obvious facts about a project
- Completed features or milestones
- When the user says "remember this" or "note that"
Fallback
If memrain tools are unavailable (server down, 401 = token rotated — re-register the MCP server), say so and continue without blocking. The MCP registration (URL + token) lives in the editor's MCP config — no secret belongs in this repo.
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 Changed · +16 lines · +191 tokens per session 5aa2e94b0933
- 16d ago First seen · 49 lines · 377 tokens per session scan A e9d9c64d2b77
memrain is a cursor rule published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 2d ago), licensed MIT. It adds 568 tokens to every session, about $0.0023 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-10-01.
Other cursor rules, from other repositories
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
170-protocol-enforcement-mechanisms
description: WHEN executing commands ENFORCE protocol compliance for memory bank operations globs: ["/.md", "/.mdc"] alwaysApply: true.
130-validation-reporting-system
description: WHEN verification completes GENERATE comprehensive reports on memory bank health globs: ["/.md", "/.mdc"] alwaysApply: true.
140-unified-command-interface
WHEN processing commands APPLY unified interface patterns for consistent memory bank operations.
150-standard-initialization-procedure
WHEN starting a new session EXECUTE initialization procedure to establish memory context.
110-automated-consistency-checks
description: WHEN verifying memory bank ENSURE consistency across related files and sections globs: ["/.md", "/.mdc"] alwaysApply: true.