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/reflect-mode-mapgit 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/reflect-mode-map)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/reflect-mode-map"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/reflect-mode-map.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.01718 | $0.01718 |
| Opus 5 | $0.00859 | $0.00859 |
| Sonnet 5 | $0.00344 | $0.00344 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
reflect-mode-map 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
4 near-identical copies found in the catalogue:
- reflect-mode-map — 100% identical, 0 lines differ
- reflect-mode-map — 100% identical, 0 lines differ
- reflect-mode-map — 100% identical, 0 lines differ
- reflect-mode-map — 95% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REFLECT MODE: TASK REVIEW PROCESS MAP
TL;DR: This visual map guides the REFLECT mode process, focusing on structured review of the implementation, documenting lessons learned, and preparing insights for future reference.
🧭 REFLECT MODE PROCESS FLOW
graph TD
Start["START REFLECT MODE"] --> ReadTasks["Read tasks.md<br>and progress.md"]
%% Initial Assessment
ReadTasks --> VerifyImplement{"Implementation<br>Complete?"}
VerifyImplement -->|"No"| ReturnImplement["Return to<br>IMPLEMENT Mode"]
VerifyImplement -->|"Yes"| AssessLevel{"Determine<br>Complexity Level"}
%% Level-Based Reflection
AssessLevel -->|"Level 1"| L1Reflect["LEVEL 1 REFLECTION<br>Level1/reflection-basic.md"]
AssessLevel -->|"Level 2"| L2Reflect["LEVEL 2 REFLECTION<br>Level2/reflection-standard.md"]
AssessLevel -->|"Level 3"| L3Reflect["LEVEL 3 REFLECTION<br>Level3/reflection-comprehensive.md"]
AssessLevel -->|"Level 4"| L4Reflect["LEVEL 4 REFLECTION<br>Level4/reflection-advanced.md"]
%% Level 1 Reflection (Quick)
L1Reflect --> L1Review["Review<br>Bug Fix"]
L1Review --> L1Document["Document<br>Solution"]
L1Document --> L1Update["Update<br>tasks.md"]
%% Level 2 Reflection (Standard)
L2Reflect --> L2Review["Review<br>Enhancement"]
L2Review --> L2WWW["Document<br>What Went Well"]
L2WWW --> L2Challenges["Document<br>Challenges"]
L2Challenges --> L2Lessons["Document<br>Lessons Learned"]
L2Lessons --> L2Update["Update<br>tasks.md"]
%% Level 3-4 Reflection (Comprehensive)
L3Reflect & L4Reflect --> L34Review["Review Implementation<br>& Creative Phases"]
L34Review --> L34Plan["Compare Against<br>Original Plan"]
L34Plan --> L34WWW["Document<br>What Went Well"]
L34WWW --> L34Challenges["Document<br>Challenges"]
L34Challenges --> L34Lessons["Document<br>Lessons Learned"]
L34Lessons --> L34ImproveProcess["Document Process<br>Improvements"]
L34ImproveProcess --> L34Update["Update<br>tasks.md"]
%% Completion & Transition
L1Update & L2Update & L34Update --> CreateReflection["Create<br>reflection.md"]
CreateReflection --> UpdateSystem["Update System<br>Documentation"]
UpdateSystem --> Transition["NEXT MODE:<br>ARCHIVE MODE"]
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 · 229 lines · 1,718 tokens per session scan A 21d71504b00a
reflect-mode-map is a cursor rule published in the GitHub repository bia-technologies/yaxunit (322 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,718 tokens to every session, about $0.0086 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.
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.
tester
Tester role - Unit, E2E, and visual regression testing.