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 skills/yellow-hammer/skills-onescript/onescript-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/skills/yellow-hammer/skills-onescript/onescript-tests)<a href="https://agentmods.dev/skills/yellow-hammer/skills-onescript/onescript-tests"><img src="https://agentmods.dev/badge/skills/yellow-hammer/skills-onescript/onescript-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/skills/yellow-hammer/skills-onescript/onescript-tests"><img src="https://agentmods.dev/badge/skills/yellow-hammer/skills-onescript/onescript-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.00059 | $0.01027 |
| Opus 5.5 | $0.00024 | $0.00411 |
| Sonnet 5.5 | $0.00012 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
onescript-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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Тесты OneScript
Новый пакет на OneUnit: в packagedef стоят .РазработкаЗависитОт("oneunit") и .РазработкаЗависитОт("asserts"). Если в манифесте уже 1testrunner, оставайся на нём и не переписывай набор на OneUnit. В oscript-library так чаще, чем OneUnit. У части пакетов раннера в манифесте нет: не добавляй его сам.
opm test и opm run test оба запускают tasks/test.os. В пакете на OneUnit скрипт вызывает локальный раннер:
oscript_modules/bin/oneunit execute -d ./tests --junit out/junit.xml
На Windows это oscript_modules\bin\oneunit.bat. Если в packagedef указан 1testrunner, tasks/test.os поднимает Новый Тестер, а не oneunit execute. Этот скрипт не заменяй. Длинный текущий каталог даёт PathTooLongException. Обход: subst на короткий диск, прогон, затем снять диск.
Файл теста
#Использовать asserts
#Использовать "../src"
&Тест
&ОтображаемоеИмя("Человекочитаемое описание проверки")
Процедура ИмяТеста() Экспорт
Ожидаем.Что(Результат, "пояснение").Равно(Эталон);
КонецПроцедуры
Аннотации ниже относятся к OneUnit. &Тест и Ожидаем.Что пишут оба раннера: по ним раннер не выбрать, смотри packagedef.
OneUnit: &ПараметризованныйТест, &ИсточникЗначение, &ПередКаждым, &ПослеКаждого, &ПередВсеми, &ПослеВсех, &ОтображаемоеИмя, &Выключен, &Тег. Обнаружитель oneunit не вызывает ПолучитьСписокТестов.
Проверки: Ожидаем.Что(X).Равно(Y), .ЭтоИстина(), .ЭтоЛожь(), .ЭтоНеопределено(), .Содержит(...), .Больше(...), .Не_(). Исключение: Ожидаем.Что(Объект).Метод("Имя", МассивПараметров).ВыбрасываетИсключение().
&ПередВсеми не сохраняет состояние: OneUnit создаёт новый экземпляр набора на каждый тест, переменная модуля из &ПередВсеми в тесте будет Неопределено. Инициализируй в &ПередКаждым или функцией-константой.
Фикстуры
Файл, документ, JSON, .env клади в tests/fixtures/, не строкой в коде. Путь от каталога теста. ТекущийСценарий().Каталог внутри теста указывает на tests, хотя раннер собирает точку входа во временном файле:
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 · 54 lines · 59 tokens per session scan A 8cb854809fc2
onescript-tests is a skill published in the GitHub repository yellow-hammer/skills-onescript (40 stars, last pushed 10d ago), licensed MIT. It adds 59 tokens to every session and 1,027 once invoked, about $0.0002 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-07.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…