What is yaxunit-selftests-structure?

A repository-specific guide for organising YAxUnit self-tests. It defines test-module names, object prefixes and suffixes, file settings, and registration in the 1C configuration.

Use it when creating or naming self-test modules under the tests directory or adding them to the 1C configuration.

It prevents new tests from being placed, named, or registered incorrectly. The guide focuses on test structure rather than the testing API itself.

How bia-technologies/yaxunit configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to bia-technologies/yaxunit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bia-technologies/yaxunit/develop/.agents/skills/yaxunit-selftests-structure/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bia-technologies/yaxunit

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bia-technologies/yaxunit/yaxunit-selftests-structure/github.svg)](https://agentmods.dev/skills/bia-technologies/yaxunit/yaxunit-selftests-structure)

Your own site

<a href="https://agentmods.dev/skills/bia-technologies/yaxunit/yaxunit-selftests-structure"><img src="https://agentmods.dev/badge/skills/bia-technologies/yaxunit/yaxunit-selftests-structure/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bia-technologies/yaxunit/yaxunit-selftests-structure"><img src="https://agentmods.dev/badge/skills/bia-technologies/yaxunit/yaxunit-selftests-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,304 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00070	$0.01304
Opus 5.5	$0.00028	$0.00522
Sonnet 5.5	$0.00014	$0.00261
Haiku 4.5	$0.00007	$0.00130

Measured yesterday against content hash 1ba9fe5056e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

yaxunit-selftests-structure 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 yesterday.

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.

.agents/skills/yaxunit-selftests-structure/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Самотесты YAxUnit: структура каталога tests/

Правила конкретно этого репозитория. API тестирования (ИсполняемыеСценарии, регистрации, проверки, события, контекст) покрывает глобальный навык yaxunit — здесь только структура и конвенции каталога.

Именование тестовых модулей

Шаблон: [Префикс типа объекта_][Имя проверяемого объекта]{_Суффикс типа модуля} (суффикс не обязателен, но крайне желателен).

Префиксы типов объектов

Тип тестируемого объекта	Префикс	Пример
Общий модуль	`ОМ_`	ОМ_ОбщегоНазначения
Регистр бухгалтерии	`РБ_`	РБ_Хозрасчетный, РБ_Хозрасчетный_НЗ
Регистр накопления	`РН_`	РН_ОстаткиНаСкладах, РН_ОстаткиНаСкладах_ММ
Регистр расчета	`РР_`	РР_Зарплата, РР_Зарплата_НЗ
Регистр сведений	`РС_`	РС_АдресныйКлассификатор
Бизнес процесс	`БП_`	БП_Согласование
Справочник	`Спр_`	Спр_Пользователи, Спр_Пользователи_МО
План счетов	`ПС_`	ПС_Хозрасчетный
План видов расчета	`ПВР_`	ПВР_Зарплатный
План видов характеристик	`ПВХ_`	ПВХ_Субконто, ПВХ_Субконто_ММ
Документ	`Док_`	Док_ПКО
Перечисление	`Пер_`	Пер_СтатусСогласования
План обмена	`ПО_`	ПО_РИБ, ПО_РИБ_ММ
Задача	`Зад_`	Зад_Задача
Обработка	`Обр_`	Обр_ЗакрытиеМесяца, Обр_ЗакрытиеМесяца_МО
Отчет	`Отч_`	Отч_УниверсальныйОтчет

Суффиксы типов модулей

Тип тестируемого модуля	Суффикс	Пример
Общий модуль	`<Без суффикса>`	ОМ_ОбщегоНазначения
Модуль объекта	`_МО`	Спр_Пользователи_МО, Обр_ЗакрытиеМесяца_МО
Модуль менеджера	`_ММ`	ПВХ_Субконто_ММ, ПО_РИБ_ММ
Модуль набора записей	`_НЗ`	РБ_Хозрасчетный_НЗ, РР_Зарплата_НЗ

Пример: для документа ПоступлениеДенег — Док_ПоступлениеДенег в tests/src/CommonModules/Док_ПоступлениеДенег/Module.bsl.

Создание нового тестового модуля

Тесты — общие модули в tests/src/CommonModules/. Для нового модуля создай файлы, если отсутствуют:

Каталог tests/src/CommonModules/[Имя модуля]
Описание tests/src/CommonModules/[Имя модуля]/[Имя модуля].mdo:
```
<?xml version="1.0" encoding="UTF-8"?>
<mdclass:CommonModule xmlns:mdclass="http://g5.1c.ru/v8/dt/metadata/mdclass" uuid="{uuidgen}">
<name>[Имя модуля]</name>
<clientManagedApplication>true</clientManagedApplication>
<server>true</server>
<clientOrdinaryApplication>true</clientOrdinaryApplication>
</mdclass:CommonModule>
```
- Не обновляй существующий .mdo — только создавай отсутствующий.
- Для модулей объектов и менеджеров (_МО, _ММ): <server>true</server>, остальные флаги false.
- Для общих (ОМ_): флаги clientManagedApplication, server, clientOrdinaryApplication — в соответствии с настройками проверяемого модуля.
Модуль tests/src/CommonModules/[Имя модуля]/Module.bsl
Обязательно зарегистрируй модуль в tests/src/Configuration/Configuration.mdo — без этого EDT его не увидит.

Read the full file on GitHub · 73 lines

Changes

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.

yesterday First seen · 73 lines · 70 tokens per session scan A 1ba9fe5056e2

Subscribe to this mod's changes

yaxunit-selftests-structure is a skill published in the GitHub repository bia-technologies/yaxunit (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 1,304 once invoked, about $0.0003 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-10-28.

1c-enterprise Testing Unit testing hacktoberfest hacktoberfest2022 yaxunit

author-test

Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.

Azure/azure-sdk-for-net · 68 tokens

edt-mcp-project-yaxunit

Discover, run, debug, poll, and cancel YAXUnit tests through current EDT-MCP launch and background-job contracts. Not for generic UI tests.

DitriXNew/EDT-MCP · 39 tokens

test-writing

A guide for writing YaxUnit tests, including test doubles called mocks and checks called assertions, for BSL code.

SteelMorgan/1c-agent-based-dev-framework · 17 tokens

yaxunit-isolation

A testing skill for YaxUnit database-writing tests that uses transactions. A transaction groups database changes so they can be handled as one unit during a test.

SteelMorgan/1c-agent-based-dev-framework · 15 tokens

1c-test-runner

A testing skill for running and writing unit tests for 1C modules, including verification through the 1C debugging tools.

Arman-Kudaibergenov/1c-ai-development-kit · 88 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

yaxunit: Skill for Claude Code