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 erf-buildgit 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/erf-build)<a href="https://agentmods.dev/skills/timoshinoleg-eng/1c-ai-workbench/erf-build"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/erf-build/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/erf-build"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/erf-build.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.00047 | $0.00943 |
| Opus 5 | $0.00023 | $0.00472 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
erf-build 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 10d 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
95% identical to erf-build — 16 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/erf-build — Сборка отчёта
Usage
/erf-build <ReportName> [SrcDir] [OutDir]
| Параметр | Обязательный | По умолчанию | Описание |
|---|---|---|---|
| ReportName | да | — | Имя отчёта (имя корневого XML) |
| SrcDir | нет | src |
Каталог исходников |
| OutDir | нет | build |
Каталог для результата |
Параметры подключения (опционально)
Предпочтительно использовать конкретную базу — это надёжнее и не требует создания временной базы.
- Прочитай
.v8-project.jsonиз корня проекта. Возьмиv8pathи разреши базу: - Если пользователь указал параметры подключения (путь, сервер) — используй напрямую
- Если указал базу по имени — ищи по id / alias / name в
.v8-project.json - Если не указал — сопоставь текущую ветку Git с
databases[].branches - Если ветка не совпала — используй
default - Если
.v8-project.jsonнет или база не найдена — не указывай параметры подключения: скрипт автоматически создаст временную базу. Для ERF со ссылочными типами (CatalogRef, DocumentRef и т.д.) генерируются заглушки метаданных. Временная база удаляется после сборки.
Если v8path не задан — скрипт сам попытается определить платформу (.v8-project.json → Program Files).
Если использованная база не зарегистрирована — после выполнения предложи добавить через /db-list add.
Команда
Используй общий скрипт из epf-build:
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/../epf-build/scripts/epf-build.ps1" <параметры>
Параметры скрипта
| Параметр | Обязательный | Описание |
|---|---|---|
-V8Path <путь> |
нет | Каталог bin платформы (или полный путь к 1cv8.exe) |
-InfoBasePath <путь> |
* | Файловая база |
-InfoBaseServer <сервер> |
* | Сервер 1С (для серверной базы) |
-InfoBaseRef <имя> |
* | Имя базы на сервере |
-UserName <имя> |
нет | Имя пользователя |
-Password <пароль> |
нет | Пароль |
-SourceFile <путь> |
да | Путь к корневому XML-файлу исходников |
-OutputFile <путь> |
да | Путь к выходному ERF-файлу |
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.
- 10d ago First seen · 72 lines · 47 tokens per session scan A 2c7fbdd9922b
erf-build is a skill published in the GitHub repository timoshinoleg-eng/1c-ai-workbench (0 stars, last pushed 23d ago), licensed MIT. It adds 47 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to erf-build, differing in 16 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.