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/bia-technologies/yaxunit/mode-transition-optimizationgit 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/mode-transition-optimization)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/mode-transition-optimization"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/mode-transition-optimization.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.02384 | $0.02384 |
| Opus 5 | $0.01192 | $0.01192 |
| Sonnet 5 | $0.00477 | $0.00477 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
mode-transition-optimization 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 2d 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:
- mode-transition-optimization — 100% identical, 0 lines differ
- mode-transition-optimization — 100% identical, 0 lines differ
- mode-transition-optimization — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MODE TRANSITION OPTIMIZATION
TL;DR: This file implements optimized mode transitions to preserve context efficiently between different phases of the Memory Bank system.
🔄 UNIFIED CONTEXT TRANSFER PROTOCOL
graph TD
Start["Mode A"] --> Create["Create Context<br>Summary Document"]
Create --> Store["Store Critical<br>Context Data"]
Store --> Transition["Transition<br>to Mode B"]
Transition --> Verify["Verify Context<br>Availability"]
Verify --> Load["Load Relevant<br>Context Data"]
Load --> Continue["Continue in<br>Mode B"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Create fill:#ffa64d,stroke:#cc7a30,color:white
style Store fill:#4dbb5f,stroke:#36873f,color:white
style Transition fill:#d94dbb,stroke:#a3378a,color:white
style Verify fill:#4dbbbb,stroke:#368787,color:white
style Load fill:#d971ff,stroke:#a33bc2,color:white
style Continue fill:#ff71c2,stroke:#c23b8a,color:white
📊 CONTEXT TRANSITION DOCUMENT
Create a standardized transition document when switching modes:
# MODE TRANSITION: [Source Mode] → [Target Mode]
## Context Summary
- Task: [Task name/description]
- Complexity: Level [1-4]
- Current Phase: [Phase name]
- Progress: [Percentage or status]
## Key Decisions
- [Decision 1]: [Brief summary]
- [Decision 2]: [Brief summary]
- [Decision 3]: [Brief summary]
## Critical Context
- [Context item 1]: [Value/status]
- [Context item 2]: [Value/status]
- [Context item 3]: [Value/status]
## Next Steps
1. [Next step 1]
2. [Next step 2]
3. [Next step 3]
## Resource Pointers
- [Resource 1]: [Location]
- [Resource 2]: [Location]
- [Resource 3]: [Location]
🔍 MODE-SPECIFIC TRANSITION HANDLERS
VAN → PLAN Transition
### VAN → PLAN
- Context preserved: Complexity level, platform detection, file structure
- Files transferred: tasks.md (initialized), activeContext.md (initialized)
- Rule optimization: Pre-load planning rules based on complexity level
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.
- 2d ago First seen · 361 lines · 2,384 tokens per session scan A 1b24d8ee78bc
mode-transition-optimization is a cursor rule published in the GitHub repository bia-technologies/yaxunit (322 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,384 tokens to every session, about $0.0119 per session on Opus 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.
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
testing
Guide for writing pytest unit and integration tests.
testing
Testing with @iobroker/testing and Mocha.