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 cleverence-mslxgit 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/cleverence-mslx)<a href="https://agentmods.dev/skills/desko77/cursor-1c-skills/cleverence-mslx"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/cleverence-mslx/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/cleverence-mslx"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/cleverence-mslx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00007 | $0.03010 |
| Opus 5 | $0.00003 | $0.01505 |
| Sonnet 5 | $0.00001 | $0.00602 |
| Haiku 4.5 | $0.00001 | $0.00301 |
Grade A, and why
cleverence-mslx 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
88% identical to cleverence-mslx — 126 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cleverence Mobile SMARTS (.mslx) configuration
Cleverence "Склад 15" / "Магазин 15" runs handheld-terminal (ТСД) logic as algorithms:
a directed graph of actions. The Mobile SMARTS Panel stores each document type and
each operation as a single-line XML file with the .mslx extension. Editing these by eye
is error-prone; the failures are almost always broken transitions or wrong variable /
field names, not XML syntax. This skill encodes how the graph works and how to change it
without breaking it.
Mental model
- DocumentType
.mslx(подDocuments/DocumentTypes/...) - a whole terminal workflow (e.g. "Сборка контейнера"). Its root is<DocumentType>. - Operation
.mslx(подDocuments/Operations/...) - a reusable sub-routine called by documents or other operations. Root is<Operation>. - Both contain
<Actions>- the ordered list of graph nodes. - The Panel and the MS Server work off a server database, not necessarily the git working copy. Editing a file on disk changes nothing until the config is transferred to the server (Сервис -> Сравнение конфигураций, or copying into the live DB + restart). If the Panel shows old behaviour after your edit, suspect a stale/never-transferred file before suspecting your change.
The single most important rule: CL_ copies of vendor operations
Vendor operations (typical Cleverence обработчики, usually under Operations/EN/...,
Operations/Основные/... etc.) get overwritten on Cleverence updates. Editing them
directly is like editing a vendor 1C extension - your change disappears on the next update.
So:
| What | Rule |
|---|---|
| Our own document type (e.g. "Сборка контейнера") | Edit in place. Do not clone. |
Our own operation (in the project root Operations/) |
Edit in place. |
| A vendor/typical operation we need to change | Make a copy CL_<Name> (placement below), edit the copy, and in the caller switch operationName to CL_<Name>. |
| A new operation | Prefix CL_ (latin). |
What ships with it
4 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 · 199 lines · 7 tokens per session scan A c9d9c3e37d10
cleverence-mslx is a skill published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 8d ago), licensed MIT. It adds 7 tokens to every session and 3,010 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to cleverence-mslx, differing in 126 lines, and is treated as a copy.
Other skills, from other repositories
cleverence-mslx
A guide for safely editing Cleverence Mobile SMARTS configuration files. Cleverence runs workflows on handheld warehouse terminals, and its .mslx files describe those workflows as connected actions.
1c-bsl-validate
A checker for calls to shared 1C modules, using an exported configuration index. Shared modules are reusable code units that other parts of a 1C application can call.
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.
1c-meta-validate
A checker for XML metadata objects in a 1C configuration. Metadata describes parts of a 1C application, such as catalogues, documents, registers, and their fields.
1c-subsystem-validate
A validator for the XML file that defines a 1C subsystem. It checks the structure and can compare the subsystem's contents with objects in the full configuration.
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.