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 skd-compilegit 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/skd-compile)<a href="https://agentmods.dev/skills/timoshinoleg-eng/1c-ai-workbench/skd-compile"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/skd-compile/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/timoshinoleg-eng/1c-ai-workbench/skd-compile"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/skd-compile.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.00041 | $0.05220 |
| Opus 5 | $0.00020 | $0.02610 |
| Sonnet 5 | $0.00008 | $0.01044 |
| Haiku 4.5 | $0.00004 | $0.00522 |
Grade A, and why
skd-compile 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 11d 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 skd-compile — 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.
How it starts
The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skd-compile — генерация СКД из JSON DSL
Принимает JSON-определение схемы компоновки данных → генерирует Template.xml (DataCompositionSchema).
Параметры и команда
| Параметр | Описание |
|---|---|
DefinitionFile |
Путь к JSON-файлу с определением СКД (взаимоисключающий с Value) |
Value |
JSON-строка с определением СКД (взаимоисключающий с DefinitionFile) |
OutputPath |
Путь к выходному Template.xml |
# Из файла
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/skd-compile.ps1" -DefinitionFile "<json>" -OutputPath "<Template.xml>"
# Из строки (без промежуточного файла)
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/skd-compile.ps1" -Value '<json-string>' -OutputPath "<Template.xml>"
JSON DSL — краткий справочник
Справочник ниже. Все примеры компилируемы как есть.
Корневая структура
{
"dataSets": [...],
"calculatedFields": [...],
"totalFields": [...],
"parameters": [...],
"templates": [...],
"groupTemplates": [...],
"dataSetLinks": [...],
"settingsVariants": [...]
}
Умолчания: dataSources → авто ИсточникДанных1/Local; settingsVariants → авто "Основной" с деталями.
Наборы данных
Тип по ключу: query → DataSetQuery, objectName → DataSetObject, items → DataSetUnion.
{ "name": "Продажи", "query": "ВЫБРАТЬ ...", "fields": [...] }
Запрос поддерживает @file — ссылку на внешний .sql файл вместо inline-текста: "query": "@queries/sales.sql". Путь разрешается относительно JSON-файла, затем CWD.
DataSetObject — внешний набор данных (без источника-запроса). Поля описываются явно; данные передаются вторым параметром ПроцессорКомпоновкиДанных.Инициализировать(Макет, Новый Структура("<objectName>", ТЗ), ...).
{ "name": "ЖурналОшибок", "objectName": "ЖурналОшибок", "fields": [
{ "field": "ТекстСообщения", "title": "Текст сообщения", "type": "string(150)" },
{ "field": "Расшифровка", "title": "Описание", "type": "CatalogRef.СтруктураПредприятия" }
]}
What ships with it
3 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.
- 11d ago First seen · 437 lines · 41 tokens per session scan A 8eb108e5ab66
skd-compile is a skill published in the GitHub repository timoshinoleg-eng/1c-ai-workbench (0 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 5,220 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 skd-compile, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
onec-selective-export
Export and inspect only the 1C:Enterprise configuration metadata objects required for a task using Designer /DumpConfigToFiles -listFile. Use when asked to study a configuration, locate BSL logic, inspect a catalog, document, register, form, command, or module, or gather dependencies without dumping the whole…
onec-dev
Route safe 1C:Enterprise development work involving an infobase, configuration metadata, selective object export, configuration extensions, Designer batch mode, BSL changes, or extension testing. Use this as the entry point when a request spans several 1C workflows or does not clearly match one focused 1C skill.
onec-extension-lifecycle
Create, dump, edit, load, back up, roll back, and delete one named 1C:Enterprise configuration extension while preserving the main configuration. Use for .cfe files, extension source trees, new customization extensions, or changes to an existing extension.
onec-extension-validate
Validate a named 1C:Enterprise configuration extension through BSL module checks, full configuration checks, applicability checks, database update, and database .cfe verification. Use after creating or modifying an extension, when diagnosing why an extension cannot be applied, or before declaring extension work…
composing-1c-queries
A guide for writing queries in the 1C:Enterprise query language. It covers how to select, filter, join, group, and summarize data from 1C catalogs, documents, and registers.
humanize-ai-text
A writing aid for rewriting text produced by language-model agents into a more natural human style. It keeps the original meaning, facts, numbers, and technical terms.