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 timoshinoleg-eng/1c-ai-workbench --skill interface-validategit clone --depth 1 https://github.com/timoshinoleg-eng/1c-ai-workbenchWrote 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/timoshinoleg-eng/1c-ai-workbench/interface-validate)<a href="https://agentmods.dev/skills/timoshinoleg-eng/1c-ai-workbench/interface-validate"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/interface-validate.svg" alt="Measured on agentmods" 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.00033 | $0.00329 |
| Opus 5 | $0.00016 | $0.00164 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
interface-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 7d 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.
This is a copy
100% identical to interface-validate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/interface-validate — валидация CommandInterface.xml
Проверяет XML командного интерфейса на структурные ошибки: корневой элемент, допустимые секции, порядок, формат ссылок на команды, дубликаты.
Параметры
| Параметр | Обяз. | Умолч. | Описание |
|---|---|---|---|
| CIPath | да | — | Путь к CommandInterface.xml |
| Detailed | нет | — | Подробный вывод (все проверки, включая успешные) |
| MaxErrors | нет | 30 | Остановиться после N ошибок |
| OutFile | нет | — | Записать результат в файл (UTF-8 BOM) |
Команда
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/interface-validate.ps1" -CIPath "Subsystems/Продажи"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/interface-validate.ps1" -CIPath "Subsystems/Продажи/Ext/CommandInterface.xml"
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.
- 7d ago First seen · 30 lines · 33 tokens per session scan A c0d521daa3f5
interface-validate is a skill published in the GitHub repository timoshinoleg-eng/1c-ai-workbench (0 stars, last pushed 20d ago), licensed MIT. It adds 33 tokens to every session and 329 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to interface-validate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
1c-skd-validate
A checker for a 1C data composition schema, the XML definition that describes how a report builds and presents data. It checks structure, references, duplicate names, and optionally whether referenced objects exist in the configuration.
1c-subsystem-validate
A checker for the XML definition of a 1C subsystem. It verifies the subsystem's structure and can compare its listed contents with objects that actually exist in the configuration.
1c-cfe-validate
A validator for a CFE, the extension format used to modify a 1C configuration, that checks its XML structure and included objects.
1c-query-validate
A checker for 1C query text against an exported configuration index. It verifies that referenced tables, register tables, tabular parts, and fields exist.
cleverence-mslx
A guide for editing Cleverence Mobile SMARTS configuration files used by handheld warehouse and shop terminals. Each .mslx file describes a workflow as a sequence of actions connected like a directed graph.
1c77-dev
A development guide for 1C:Enterprise 7.7, an older version of the 1C business-application platform. It covers the version's code, forms, metadata, binary files, encoding, and command-line tools.