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 1c-subsystem-compilegit 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/1c-subsystem-compile)<a href="https://agentmods.dev/skills/desko77/cursor-1c-skills/1c-subsystem-compile"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-subsystem-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/desko77/cursor-1c-skills/1c-subsystem-compile"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-subsystem-compile.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.00046 | $0.00486 |
| Opus 5 | $0.00023 | $0.00243 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
1c-subsystem-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 6d 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.
What it actually says
/subsystem-compile - генерация подсистемы из JSON
Принимает JSON-определение подсистемы → генерирует XML + файловую структуру + регистрирует в родителе (Configuration.xml или родительская подсистема).
Параметры и команда
| Параметр | Описание |
|---|---|
DefinitionFile |
Путь к JSON-файлу определения |
Value |
Инлайн JSON-строка (альтернатива DefinitionFile) |
OutputDir |
Корень выгрузки (где Subsystems/, Configuration.xml) |
Parent |
Путь к XML родительской подсистемы (для вложенных) |
NoValidate |
Пропустить авто-валидацию |
powershell.exe -NoProfile -File 'skills/1c-subsystem-compile/scripts/subsystem-compile.ps1' -Value '<json>' -OutputDir '<ConfigDir>'
JSON-определение
{
"name": "МояПодсистема",
"synonym": "Моя подсистема",
"comment": "",
"includeInCommandInterface": true,
"useOneCommand": false,
"explanation": "Описание раздела",
"picture": "CommonPicture.МояКартинка",
"content": ["Catalog.Товары", "Document.Заказ"]
}
Минимально: только name. Остальное - дефолты.
Примеры
# Минимальная подсистема
... -Value '{"name":"Тест"}' -OutputDir config/
# С составом и картинкой
... -Value '{"name":"Продажи","content":["Catalog.Товары","Report.Продажи"],"picture":"CommonPicture.Продажи"}' -OutputDir config/
# Вложенная подсистема
... -Value '{"name":"Дочерняя"}' -OutputDir config/ -Parent config/Subsystems/Продажи.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.
- 6d ago First seen · 54 lines · 46 tokens per session scan A 3a7b04592fb3
1c-subsystem-compile is a skill published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 486 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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-meta-compile
A generator for creating 1C metadata objects from a JSON description. Metadata objects include parts of a 1C business configuration, such as catalogs, documents, registers, constants, modules, reports, and data processors.
1c-cf-new-project
A workflow for creating a new 1C configuration from an empty starting point. 1C is a platform for building business applications; a configuration defines their data, screens, permissions, and behavior.
1c-xdto-validate
A checker for 1C XDTO packages and their connection to a configuration. It reports errors that could make 1C reject the package or interpret its data incorrectly at runtime.
1c77-dev
A development guide for the older 1C:Enterprise 7.7 platform. It covers its code, forms, configuration objects, reports, and external-processing files, including their older file formats and character encoding.
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.