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/git)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/git"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/git/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/git"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/git.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.00271 | $0.00271 |
| Opus 5.5 | $0.00108 | $0.00108 |
| Sonnet 5.5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
git 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
Формат именования веток
- Используйте формат:
feature/{ISSUE_ID}-short-name - Примеры:
feature/123-add-user-authenticationfeature/456-fix-login-bugfeature/789-implement-report-generation
Формат коммитов
- Используйте формат:
#{ISSUE_ID} message - Примеры:
#123 Добавлена аутентификация пользователей#456 Исправлена ошибка входа в систему#789 Реализована генерация отчетов
Формат именования Pull Request
- Используйте формат:
ISSUE_ID / name - Примеры:
123 / Добавление аутентификации пользователей456 / Исправление ошибки входа в систему789 / Реализация генерации отчетов
Дополнительные правила
- Всегда указывайте ISSUE_ID в ветках, коммитах и PR
- Используйте понятные и описательные названия
- Следуйте принципам conventional commits для сообщений коммитов
- Обеспечивайте связь между кодом и задачами через ISSUE_ID
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 · 33 lines · 271 tokens per session scan A a28d7669408c
git is a cursor rule published in the GitHub repository bia-technologies/yaxunit (340 stars, last pushed 10d ago), licensed Apache-2.0. It adds 271 tokens to every session, about $0.0011 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
commit-checks
Run gofmt, go vet, and unit tests before committing Go files.
pre-commit-lint-format
Enforce Prettier format, ESLint lint, and unit tests before every commit in lfx-self-serve.
telegram-bot-tests
Test conventions for Telegram Bot library.
apexyard
ApexYard governance bridge for Cursor. Mechanical gates load from .claude/settings.json when third-party configs are on. This file is the advisory pointer.
hook-commits
Set up pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
beads
This project uses Beads (bd) for issue tracking.