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/fix-galo)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/fix-galo"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/fix-galo/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/fix-galo"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/fix-galo.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.00134 | $0.00134 |
| Opus 5.5 | $0.00054 | $0.00054 |
| Sonnet 5.5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
fix-galo 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.
What it actually says
SYNTAX RULES
- Правила создания массива
- Пустой массив -
Новый Массив - Массив со значениями -
ЮТКоллекции.ЗначениеВМассиве("a", "b", "c") - Приведет к ошибке -
Новый Массив("a", "b", "c")
- Пустой массив -
- CommonModule - общие модули не могут хранить переменные, в них размещаются только методы
- Methods must not return other methods
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 · 14 lines · 134 tokens per session scan A 5c7e9d66ecd9
fix-galo is a cursor rule published in the GitHub repository bia-technologies/yaxunit (341 stars, last pushed 18d ago), licensed Apache-2.0. It adds 134 tokens to every session, about $0.0005 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
121-java-unit-testing
Java Unit testing guidelines.
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.
telegram-bot-tests
Test conventions for Telegram Bot library.
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.
testing-patterns
A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.
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.