Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yellow-hammer/skills-onescriptnpx agentmods add rules/yellow-hammer/skills-onescript/os-testsWrote 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/yellow-hammer/skills-onescript/os-tests)<a href="https://agentmods.dev/rules/yellow-hammer/skills-onescript/os-tests"><img src="https://agentmods.dev/badge/rules/yellow-hammer/skills-onescript/os-tests/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/yellow-hammer/skills-onescript/os-tests"><img src="https://agentmods.dev/badge/rules/yellow-hammer/skills-onescript/os-tests.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.00413 |
| Opus 5.5 | $0.00000 | $0.00165 |
| Sonnet 5.5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
os-tests 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 9d 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
Тесты OneUnit
Запуск: opm test и opm run test вызывают tasks/test.os. На OneUnit внутри скрипта oneunit execute -d ./tests. Если в packagedef указан 1testrunner, набор остаётся на нём: скрипт создаёт Новый Тестер.
Это правило видит и файлы 1testrunner. &Тест с Ожидаем бывает у обоих раннеров. Раннер бери из packagedef. Если там 1testrunner или в файле есть ПолучитьСписокТестов, &Перед или &Параметры, аннотации &ПередКаждым и &ПараметризованныйТест не добавляй.
#Использовать asserts
#Использовать "../src"
&Тест
Процедура ИмяТеста() Экспорт
Ожидаем.Что(Результат).Равно(Эталон);
КонецПроцедуры
- Состояние из
&ПередВсемив тесте пустое. Инициализация - в&ПередКаждым. - Файлы данных клади в
tests/fixtures/, если пакет уже так устроен. Путь:ОбъединитьПути(ТекущийСценарий().Каталог, "fixtures", ИмяФайла). Меняющий тест работает на копии. - Переменную не называй
ОжидаемиУтверждения: эти имена занимаетasserts. rootLoggerвautumn-properties.jsonне повышай до WARN: прогон потеряет статистику.
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.
- 9d ago First seen · 27 lines · 0 tokens per session scan A 76cded3413ce
os-tests is a cursor rule published in the GitHub repository yellow-hammer/skills-onescript (40 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 413 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-10-07.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
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.
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
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.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.