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.
npx agentmods add rules/alkoleft/platform-context-exporter/memory-bank-pathsgit clone --depth 1 https://github.com/alkoleft/platform-context-exporterWrote 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/alkoleft/platform-context-exporter/memory-bank-paths)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/memory-bank-paths"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/memory-bank-paths.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 | $0.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
memory-bank-paths 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 3d 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.
This is a copy
100% identical to memory-bank-paths — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CORE MEMORY BANK FILE LOCATIONS
CRITICAL: All core Memory Bank files reside within the memory-bank/ directory at the project root. Do NOT create or modify these files outside this directory unless explicitly instructed for archiving purposes.
- Tasks File:
memory-bank/tasks.md- This file is used for active, in-progress task tracking, detailing steps, checklists, and component lists. Its content, particularly the detailed checklists, is merged into the main archive document for the task upon completion. After archival,tasks.mdis cleared to be ready for the next task. It is an ephemeral working document during a task's lifecycle, with its persistent record captured in the task's archive file. - Active Context File:
memory-bank/activeContext.md - Progress File:
memory-bank/progress.md - Project Brief File:
memory-bank/projectbrief.md - Product Context File:
memory-bank/productContext.md - System Patterns File:
memory-bank/systemPatterns.md - Tech Context File:
memory-bank/techContext.md - Style Guide File:
memory-bank/style-guide.md - Creative Phase Docs:
memory-bank/creative/creative-[feature_name].md - Reflection Docs:
memory-bank/reflection/reflection-[task_id].md - Archive Directory:
memory-bank/archive/archive-[task_id].md
Verification Mandate: Before any create_file or edit_file operation on these core files, verify the path starts with memory-bank/. If attempting to create a new core file (e.g., tasks.md at the start of a project), ensure it is created at memory-bank/tasks.md.
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.
- 3d ago First seen · 24 lines · 385 tokens per session scan A 4e0417364235
memory-bank-paths is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It adds 385 tokens to every session, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to memory-bank-paths, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.
1c-transactions-and-locks
Транзакции и управляемые блокировки: шаблон, порядок захвата.
1c-mdo-integrity
Целостность MDO-файлов: UUID, ссылки.
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.