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 SteelMorgan/1c-agent-based-dev-framework --skill gui-controlgit clone --depth 1 https://github.com/SteelMorgan/1c-agent-based-dev-frameworkWrote 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/steelmorgan/1c-agent-based-dev-framework/gui-control)<a href="https://agentmods.dev/skills/steelmorgan/1c-agent-based-dev-framework/gui-control"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/gui-control/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/steelmorgan/1c-agent-based-dev-framework/gui-control"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/gui-control.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.00020 | $0.01355 |
| Opus 5 | $0.00010 | $0.00678 |
| Sonnet 5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
gui-control 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 131 lines · 20 tokens per session scan A 69dd702e1eb6
gui-control is a skill published in the GitHub repository SteelMorgan/1c-agent-based-dev-framework (98 stars, last pushed 2mo ago), with no licence file. It adds 20 tokens to every session and 1,355 once invoked, about $0.0001 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
cfe-diff
A tool for analysing a 1C configuration extension, a package that adds or changes parts of a 1C business application. It can show what the extension contains or check whether its code changes were transferred into the main configuration.
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.