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 db-listgit 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/db-list)<a href="https://agentmods.dev/skills/timoshinoleg-eng/1c-ai-workbench/db-list"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/db-list/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/db-list"><img src="https://agentmods.dev/badge/skills/timoshinoleg-eng/1c-ai-workbench/db-list.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.00046 | $0.01495 |
| Opus 5 | $0.00023 | $0.00747 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
db-list 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
97% identical to 1c-db-list — 42 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/db-list — Управление реестром баз данных
Управляет файлом .v8-project.json — реестром информационных баз проекта. Файл хранит параметры подключения, алиасы, привязку к веткам Git.
Usage
/db-list — показать список баз
/db-list add — добавить базу (интерактивно)
/db-list remove <id> — удалить базу из реестра
/db-list show <id|alias> — подробности по базе
Формат .v8-project.json
Файл размещается в корне проекта (рядом с .git/).
{
"v8path": "C:\\Program Files\\1cv8\\8.3.25.1257\\bin",
"databases": [
{
"id": "dev",
"name": "Разработка",
"type": "file",
"path": "C:\\Bases\\MyApp_Dev",
"user": "Admin",
"password": "",
"aliases": ["dev", "разработка"],
"branches": ["dev", "develop", "feature/*"],
"configSrc": "C:\\WS\\myapp\\cfsrc"
},
{
"id": "test",
"name": "Тестовая",
"type": "server",
"server": "srv01",
"ref": "MyApp_Test",
"user": "Admin",
"password": "123",
"aliases": ["test", "тест"]
}
],
"default": "dev"
}
Поля корневого объекта
| Поле | Тип | Описание |
|---|---|---|
v8path |
string | Каталог bin платформы 1С. Необязательный — если не задан, автоопределение |
databases |
array | Массив баз данных |
default |
string | id базы по умолчанию |
Поля объекта базы данных
| Поле | Тип | Обязательное | Описание |
|---|---|---|---|
id |
string | да | Уникальный идентификатор (латиница, без пробелов) |
name |
string | да | Человекочитаемое имя |
type |
"file" / "server" |
да | Тип подключения |
path |
string | для file | Путь к каталогу файловой базы |
server |
string | для server | Адрес сервера 1С |
ref |
string | для server | Имя базы на сервере |
user |
string | нет | Имя пользователя 1С |
password |
string | нет | Пароль |
aliases |
string[] | нет | Альтернативные имена для быстрого доступа |
branches |
string[] | нет | Git-ветки или glob-паттерны (release/*, feature/*), привязанные к этой базе |
configSrc |
string | нет | Каталог XML-выгрузки конфигурации |
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 · 159 lines · 46 tokens per session scan A 939c570fc8f3
db-list is a skill published in the GitHub repository timoshinoleg-eng/1c-ai-workbench (0 stars, last pushed 23d ago), licensed MIT. It adds 46 tokens to every session and 1,495 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to 1c-db-list, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
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.
1c-db-create
A tool that creates a new 1C information base, either as files on a computer or as a database on a server. An information base is the 1C database that stores an organisation’s configuration and data.
1c-db-dump-xml
A command that exports a 1C information database configuration into XML source files. It supports full, incremental, partial, and configuration-information updates.
1c-db-list
A tool for managing the project registry of 1C information bases in .v8-project.json. The registry stores connection details, aliases, and links between databases and Git branches.
1c-db-update
A tool for applying a changed 1C application configuration to its database structure. This step updates the database so it matches the configuration loaded into 1C.
1c-query-validate
A checker for 1C database queries. It compares the tables, records, virtual tables, and fields named in a query with an index of the 1C configuration.