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/bia-technologies/yaxunitWrote 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/bia-technologies/yaxunit/memory-bank-paths)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/memory-bank-paths"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/memory-bank-paths/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/bia-technologies/yaxunit/memory-bank-paths"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/memory-bank-paths.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.00385 | $0.00385 |
| Opus 5.5 | $0.00154 | $0.00154 |
| Sonnet 5.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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- memory-bank-paths — 100% identical, 0 lines differ
- memory-bank-paths — 100% identical, 0 lines differ
- memory-bank-paths — 97% identical, 2 lines differ
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.
- 1mo ago First seen · 24 lines · 385 tokens per session scan A 4e0417364235
memory-bank-paths is a cursor rule published in the GitHub repository bia-technologies/yaxunit (341 stars, last pushed 18d ago), licensed Apache-2.0. It adds 385 tokens to every session, about $0.0015 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-09-01.
Other cursor rules, from other repositories
telegram-bot-tests
Test conventions for Telegram Bot library.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
121-java-unit-testing
Java Unit testing guidelines.
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.