onec-extension-lifecycle

onec-extension-lifecycle is a skill for Claude Code, Codex from Muredsa/1C-Enterprise-Agent-Toolkit. It costs 59 tokens per session (509 once invoked), scanned A, original, MIT.

A workflow for creating and changing one named 1C:Enterprise configuration extension while leaving the main configuration unchanged. 1C:Enterprise is business software whose behavior is defined by configurable metadata and code.

In plain words
What is it for?
It helps scaffold new extensions, dump existing ones into editable source files, load .cfe extension files, edit XML and BSL code, and test changes.
Why use it?
It provides an isolated, auditable way to inspect, edit, load, back up, roll back, and delete extensions without directly changing the main configuration.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: $skill-name invocation.

Part of the onec-dev-toolkit plugin — 4 skills shipped together

Good fit It helps scaffold new extensions, dump existing ones into editable source files, load .cfe extension files, edit XML and BSL code, and test changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle
Install

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.

Any agent
npx skills add Muredsa/1C-Enterprise-Agent-Toolkit --skill onec-extension-lifecycle
Clone the repo
git clone --depth 1 https://github.com/Muredsa/1C-Enterprise-Agent-Toolkit

Made for: Claude Code, Codex.

Or install onec-dev-toolkit, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for onec-extension-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle/github.svg)](https://agentmods.dev/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle"><img src="https://agentmods.dev/badge/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle/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.

agentmods 80×15 button for onec-extension-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle"><img src="https://agentmods.dev/badge/skills/muredsa/1c-enterprise-agent-toolkit/onec-extension-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 509 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.00509
Opus 5 $0.00030 $0.00254
Sonnet 5 $0.00012 $0.00102
Haiku 4.5 $0.00006 $0.00051

Measured 10d ago against content hash cacef8d67a8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

onec-extension-lifecycle 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 10d 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.

skills/onec-extension-lifecycle/SKILL.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

1C Extension Lifecycle

Keep all customization in one explicitly named extension and use an isolated session by default.

Choose the path

  • For a new extension, run extension-scaffold. It selectively reads Configuration and its exact default Language.*, creates a mapped adopted language with a distinct extension UUID, and creates a hierarchical source tree with one native server common module and a smoke-test function.
  • For an existing extension in the infobase, run extension-dump to get editable hierarchical sources before changing code.
  • For an existing .cfe, run extension-load-cfe only after identifying the exact target extension name.

Read references/transaction-model.md before loading or deleting anything.

Implement a change

  1. Run extension-list and record whether the exact extension name already exists.
  2. Create or dump the source tree inside the session. Let the scaffold command derive the controlled DefaultLanguage; never hardcode it from a different configuration.
  3. Inspect only the required main-configuration objects with $onec-selective-export.
  4. Edit extension XML and BSL. Keep the extension name and prefix stable. Do not edit the main configuration dump.
  5. Run extension-load-files --name <name> --source <directory>. The CLI automatically backs up both editable and database forms before replacing a pre-existing extension.
  6. Delegate checks and database update to $onec-extension-validate.

Recover

  • Before database update, run extension-rollback to restore the extension configuration from its database configuration.
  • For a new session-created extension, run extension-delete --name <name> --confirm-name <name> when abandoning the change.
  • For a pre-existing extension, restore the automatic backup rather than deleting it. Never use --allow-existing without a separate explicit request to delete that exact extension.
  • Finish with the router's session-cleanup; this removes sources, dumps, backups, logs, and the sandbox infobase owned by the session.

Read the full file on GitHub · 35 lines

Files

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.

Changes

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.

  1. 10d ago First seen · 35 lines · 59 tokens per session scan A cacef8d67a8a

Subscribe to this mod's changes

onec-extension-lifecycle is a skill published in the GitHub repository Muredsa/1C-Enterprise-Agent-Toolkit (21 stars, last pushed 28d ago), licensed MIT. It adds 59 tokens to every session and 509 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories