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/Desko77/cursor-1c-skillsWrote 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/desko77/cursor-1c-skills/testing-patterns)<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/testing-patterns"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/testing-patterns/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/desko77/cursor-1c-skills/testing-patterns"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/testing-patterns.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.00000 | $0.00885 |
| Opus 5.5 | $0.00000 | $0.00354 |
| Sonnet 5.5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
testing-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1C Testing Patterns
Шаблоны и подходы к тестированию кода 1С.
Применяется: при написании тестов для кода 1С.
YaXUnit - юнит-тесты
Шаблон теста
Процедура Тест<ИмяФункции>_<Сценарий>() Экспорт
// Arrange
<подготовка данных>
// Act
Результат = <вызов тестируемой функции>;
// Assert
ЮТест.ОжидаетЧто(Результат).<проверка>;
КонецПроцедуры
Пример
Процедура ТестПолучениеДанныхКлиента_СуществующийКлиент() Экспорт
// Arrange
Клиент = Справочники.Клиенты.СоздатьЭлемент();
Клиент.Наименование = "Тест";
Клиент.Записать();
// Act
Данные = ПолучитьДанныеКлиента(Клиент.Ссылка);
// Assert
ЮТест.ОжидаетЧто(Данные).Свойство("Наименование").Равно("Тест");
КонецПроцедуры
Именование тестов
Тест<Функция>_<Сценарий>- основной формат- Сценарии:
СуществующийОбъект,НесуществующийОбъект,НеверныйПараметр,ПустоеЗначение,ГраничноеУсловие
Vanessa Automation - BDD-тесты
Шаблон сценария
Функционал: <Название функциональности>
Сценарий: <Описание сценария>
Дано <начальное состояние>
Когда <действие пользователя>
Тогда <ожидаемый результат>
Пример
Функционал: Создание заказа клиента
Сценарий: Создание нового заказа
Дано Я авторизован как "Менеджер"
И Существует клиент "ООО Тест"
Когда Я открываю форму создания документа "ЗаказКлиента"
И Я выбираю клиента "ООО Тест"
И Я добавляю товар "Товар1" с количеством "10"
И Я нажимаю "Провести"
Тогда Документ "ЗаказКлиента" проведен
И Остатки товара "Товар1" уменьшились на "10"
Типы тест-кейсов
Для каждой тестируемой функции генерировать:
- Happy path - нормальный сценарий, корректные данные
- Edge cases - граничные условия (пустая строка, 0, максимальное значение)
- Error cases - невалидные данные, несуществующие ссылки
- Boundary conditions - NULL, Неопределено, пустые коллекции
Цели покрытия
| Область | Цель |
|---|---|
| Экспортные функции (public API) | 100% |
| Бизнес-логика (расчеты, валидация) | 90% |
| Утилитарные функции | 80% |
| Обработчики UI | 70% |
| Общее покрытие | 80% |
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 · 116 lines · 0 tokens per session scan A 42098ac46f27
testing-patterns is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (69 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 885 tokens. 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-08-30.
Other cursor rules, from other repositories
jsdoc
A set of JSDoc rules for documenting JavaScript or TypeScript code, with comments written in Russian.
project-context
Technical context for a VS Code extension that exposes 1C Platform Tools to AI agents through an MCP server. The extension communicates with the standalone server over IPC, while the server registers one agent tool for each available 1C command.
code-style
Project rules for code style, commit messages, comments, interface text, logs, TypeScript, and documentation. They require Russian text in user-facing and code-comment contexts, along with strict TypeScript practices.
naming-abbreviations
A set of project rules for naming 1C Platform Tools and its MCP tools. It defines allowed short forms and limits the combined server and tool name to 60 characters.
evolution-no-legacy
A coding rule for changing software interfaces and configuration names without keeping old names working by default.
121-java-unit-testing
Java Unit testing guidelines.