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/reflection-basic)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/reflection-basic"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/reflection-basic/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/reflection-basic"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/reflection-basic.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.01232 | $0.01232 |
| Opus 5.5 | $0.00493 | $0.00493 |
| Sonnet 5.5 | $0.00246 | $0.00246 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
reflection-basic 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:
- reflection-basic — 100% identical, 0 lines differ
- reflection-basic — 100% identical, 0 lines differ
- reflection-basic — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BASIC REFLECTION FOR LEVEL 2 TASKS
TL;DR: This document outlines a basic reflection approach for Level 2 (Simple Enhancement) tasks, ensuring that key insights and lessons are captured without unnecessary overhead.
🔍 REFLECTION OVERVIEW
Reflection is essential for improving future work, even for simpler Level 2 enhancements. This basic reflection approach focuses on key outcomes, challenges, and lessons learned while maintaining efficiency.
📋 REFLECTION PRINCIPLES
- Honesty: Accurately represent successes and challenges
- Specificity: Include concrete examples and observations
- Insight: Go beyond surface observations to derive useful insights
- Improvement: Focus on actionable takeaways for future work
- Efficiency: Keep reflection concise and focused on key learnings
📋 BASIC REFLECTION STRUCTURE
# Level 2 Enhancement Reflection: [Feature Name]
## Enhancement Summary
[Brief one-paragraph summary of the enhancement]
## What Went Well
- [Specific success point 1]
- [Specific success point 2]
- [Specific success point 3]
## Challenges Encountered
- [Specific challenge 1]
- [Specific challenge 2]
- [Specific challenge 3]
## Solutions Applied
- [Solution to challenge 1]
- [Solution to challenge 2]
- [Solution to challenge 3]
## Key Technical Insights
- [Technical insight 1]
- [Technical insight 2]
- [Technical insight 3]
## Process Insights
- [Process insight 1]
- [Process insight 2]
- [Process insight 3]
## Action Items for Future Work
- [Specific action item 1]
- [Specific action item 2]
- [Specific action item 3]
## Time Estimation Accuracy
- Estimated time: [X hours/days]
- Actual time: [Y hours/days]
- Variance: [Z%]
- Reason for variance: [Brief explanation]
📋 REFLECTION QUALITY
High-quality reflections for Level 2 tasks should:
- Provide specific examples rather than vague statements
- Identify concrete takeaways not general observations
- Connect challenges to solutions with clear reasoning
- Analyze estimation accuracy to improve future planning
- Generate actionable improvements for future work
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 · 178 lines · 1,232 tokens per session scan A d65b57dfe0d7
reflection-basic is a cursor rule published in the GitHub repository bia-technologies/yaxunit (339 stars, last pushed 9d ago), licensed Apache-2.0. It adds 1,232 tokens to every session, about $0.0049 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.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.