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 Desko77/cursor-1c-skills --skill composing-1c-queriesgit clone --depth 1 https://github.com/Desko77/cursor-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/desko77/cursor-1c-skills/composing-1c-queries)<a href="https://agentmods.dev/skills/desko77/cursor-1c-skills/composing-1c-queries"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/composing-1c-queries/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/desko77/cursor-1c-skills/composing-1c-queries"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/composing-1c-queries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00009 | $0.07062 |
| Opus 5 | $0.00005 | $0.03531 |
| Sonnet 5 | $0.00002 | $0.01412 |
| Haiku 4.5 | $0.00001 | $0.00706 |
Grade A, and why
composing-1c-queries 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
95% identical to composing-1c-queries — 125 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composing 1C Queries
Rules and patterns for writing correct 1C:Enterprise query language (язык запросов 1С).
Queries are executed via the execute_query tool/endpoint.
CRITICAL: Verify Metadata Before Querying
NEVER guess or invent metadata object names, attribute names, or tabular section names. 1C configurations vary greatly - object and field names are unique to each database.
Before composing a query, if you are not certain about the exact names, use get_metadata or any other available tool to retrieve 1C configuration metadata to discover:
- Available metadata objects (catalogs, documents, registers, etc.)
- Object attributes (реквизиты) and their types
- Tabular sections (табличные части) and their columns
- Register dimensions, resources, and attributes
Workflow: retrieve metadata → confirm names → compose query → validate query → execute query
A query with a wrong object or field name will fail with a runtime error. Spending one call on metadata retrieval is always cheaper than debugging a failed query.
Имена таблиц и полей из AI-EDT
Если сервер AI-EDT подключен, имена не угадываются, а берутся у него - insights operation=describe_db_tables
(отдельное имя describe_db_tables тоже работает). Инструмент показывает, во что объект превращается в
базе данных: основную таблицу, по одной на каждую табличную часть, виртуальные таблицы регистра
(остатки, обороты, срезы) с их параметрами, таблицу изменений и перерасчеты регистра расчета. Имена
таблиц и полей отдаются сразу на двух языках, с типами полей, готовыми к подстановке после ИЗ.
Это дешевле, чем писать запрос по памяти и ловить ошибки имен по одной через validate_query: за один
вызов видно все, что вообще можно выбрать.
Validate Query via AI-EDT
Если сервер AI-EDT подключен (инструменты ai-edt доступны), обязательно проверяй запрос перед выполнением через validate_query:
- Проверяет синтаксис и семантику в контексте реального проекта
- Для запросов СКД:
dcsMode=true - Ловит ошибки имен таблиц, полей, типов до выполнения
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.
- 7d ago First seen · 569 lines · 9 tokens per session scan A a33386c5f37a
composing-1c-queries is a skill published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 7,062 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to composing-1c-queries, differing in 125 lines, and is treated as a copy.
Other skills, from other repositories
1c-mcp-toolkit
A local HTTP API for working with a running 1C:Enterprise database through the MCP Toolkit processing file. 1C:Enterprise is a platform for business applications, and this tool can access its live runtime context.
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.
kd2-rules
A development guide for building data-exchange rules in 1C:Enterprise Data Conversion 2.0. This software maps objects and fields between two 1C configurations and exports the resulting rules as XML.
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.