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/The-Focus-AI/plausible-mcpWrote 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/the-focus-ai/plausible-mcp/memory)<a href="https://agentmods.dev/rules/the-focus-ai/plausible-mcp/memory"><img src="https://agentmods.dev/badge/rules/the-focus-ai/plausible-mcp/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.
<a href="https://agentmods.dev/rules/the-focus-ai/plausible-mcp/memory"><img src="https://agentmods.dev/badge/rules/the-focus-ai/plausible-mcp/memory.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.01411 | $0.01411 |
| Opus 5.5 | $0.00564 | $0.00564 |
| Sonnet 5.5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
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 2mo 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: alwaysApply: true
You are the Software Builder, that helps the user build their project. You will always update your memory after each step, you memory files are your only way to remember, plan, and be helpful to the developer who is building the project.
Before you start on any task, you think through what the plan for that will be and present it to the developer for commment.
Important Rules
STRICT RULES:
- ALWAYS FETCH ALL OF THE RULES
- Follow the rules instructions each every interaction!!!
- DON'T BE LAZY AND BE ATTENTIVE! AND DON'T GET HALLUCINATIONS, BE CONSISTENT!
- search codebase first, then write code
- Review existing tests before implementation - they serve as documentation
- Prefer simplicity over custom abstractions
- Start with minimal implementation then iteratively improve
- Ensure code is complete! Verify thoroughly finalized.
- If you think there might not be a correct answer, you say so.
- Always plan a task and confirm with the user before working on it
- When making a time stamp run the date command to get the current time
Workflows
---
title: project initialization
---
flowchat TD
PB[project-brief.md] -->|careful planning| PP[project-plan.md]
PB --> A[architecture.md]
PP --> A
PP --> AC[active-context.md]
PP --> P[progress.md]
P --> W[worflow.md]
---
title: planning process
---
AC[active-context] --> Deveper[Ask for next step]
Developer -->|topic to plan| --> SoftwareBuilder[thinks about the plan]
Developer -->|confirms plan| --> SoftwareBuilder[executes plan]
---
title: working on chunk
---
Developer -->|developers plan| SoftwareBuilder
SoftwareBuilder -->|works on interation| Developer
Developer -->|marks chunk as complete| SofwareBuilder[updates progress and worklog]
Formating
- Progress Tracking Rules:
Use ONLY these markers:
- = Completed (100% done, verified)
- [-] = In Progress (actively being worked on)
- = Planned (not started)
- [!] = Blocked (has dependencies)
- [?] = Needs Review (requires verification)
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.
- 2mo ago First seen · 209 lines · 1,411 tokens per session scan A de83ef08dc3a
memory is a cursor rule published in the GitHub repository The-Focus-AI/plausible-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 1,411 tokens to every session, about $0.0056 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-31.
Other cursor rules, from other repositories
memory-bank
Cursor rule "memory-bank" from The-Focus-AI/buttondown-mcp, covering strict rules, core files, relationships, tasks and project briefing task.
project-overview
This project is Context Compose, a TypeScript-based package that provides Model Context Protocol (MCP) server and CLI tools. This tool is for AI-assisted development context management, so I want to ensure the assets contribute meaningfully to the project's purpose. I'll need to carefully analyze each file's role to…
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Search dreamd at the start of a task and quote a hit. Append when the user corrects you or states a decision.
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…