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.
npx skills add Nikolay-Shirokov/cc-1c-skills --skill skd-validategit clone --depth 1 https://github.com/Nikolay-Shirokov/cc-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/skills/nikolay-shirokov/cc-1c-skills/skd-validate)<a href="https://agentmods.dev/skills/nikolay-shirokov/cc-1c-skills/skd-validate"><img src="https://agentmods.dev/badge/skills/nikolay-shirokov/cc-1c-skills/skd-validate/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/nikolay-shirokov/cc-1c-skills/skd-validate"><img src="https://agentmods.dev/badge/skills/nikolay-shirokov/cc-1c-skills/skd-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00656 |
| Opus 5.5 | $0.00015 | $0.00262 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
skd-validate 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 27d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skd-validate — 100% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skd-validate — валидация СКД (DataCompositionSchema)
Проверяет структурную корректность Template.xml схемы компоновки данных. Выявляет ошибки формата, битые ссылки, дубликаты имён.
Параметры
| Параметр | Обяз. | Умолч. | Описание |
|---|---|---|---|
| TemplatePath | да | — | Путь к Template.xml или каталогу макета |
| Detailed | нет | — | Подробный вывод (все проверки, включая успешные) |
| MaxErrors | нет | 20 | Остановиться после N ошибок |
| OutFile | нет | — | Записать результат в файл |
Команда
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/skd-validate.ps1" -TemplatePath "src/МойОтчёт/Templates/ОсновнаяСхема"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/skd-validate.ps1" -TemplatePath "Catalogs/Номенклатура/Templates/СКД/Ext/Template.xml"
Проверка по XSD
Порядок элементов, типы и значения дополнительно сверяются с XSD-схемами платформы, если они скачаны в проект. Иначе итоговая строка заканчивается на XSD not checked: <причина> — это не «проверено всё». Когда проверка нужна (например, платформа пишет «нарушен порядок следования»), скачай схемы версии формата выгрузки — атрибут version в Configuration.xml — через /v8-xsd-fetch -Versions <версия> и запусти снова. То же при [WARN] XSD: no schemas for format <версия>.
Нарушение: XSD <версия>, line N: <родитель>/<элемент>: <что не так>.
must come before <X>— перенеси элемент непосредственно перед<X>, содержимое не меняй.duplicate— удали повтор.not allowed in <P>— элементу здесь не место. Иначе — текст о недопустимом значении.[WARN]с(no schemas for <версия>)— сверено по схемам более новой версии: ориентир, не вердикт.- Если шаблон ты только что собрал или изменил
/skd-compileили/skd-edit, нарушение — дефект навыка: сообщи о нём пользователю.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago Changed · +11 lines 8a9cbfe1960d
- 1mo ago First seen · 30 lines · 38 tokens per session scan A 2ee9ebe859c3
skd-validate is a skill published in the GitHub repository Nikolay-Shirokov/cc-1c-skills (730 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 656 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-09-03.
Other skills, from other repositories
1c-web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses scripted actions to navigate screens, fill forms, read tables and reports, and apply filters.
1c-vanessa-steps
A searchable catalogue of 1,569 Vanessa Automation steps, with tools for finding steps and checking Gherkin scenarios. Gherkin is the plain-language format used by behavior-driven tests, where each sentence maps to an implemented test action.
1c-form-validate
A checker for managed forms in 1C, a platform for building business applications. It checks a form's XML structure, identifiers, linked fields, and commands.
1c-meta-validate
A checker for 1C metadata objects stored in XML. It verifies that the object's structure is valid and can optionally compare referenced types with the wider configuration.
1c-xdto-validate
A checker for XDTO packages in 1C:Enterprise. XDTO describes the structure and data types used when 1C exchanges data with external systems.
1c-cf-validate
A validator for a 1C configuration, where 1C is a business software platform. It checks the exported configuration files for structural problems in XML, settings, languages, and object folders.