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 AndreevED/1c-ai-feature-dev-workflow --skill 1c-feature-devgit clone --depth 1 https://github.com/AndreevED/1c-ai-feature-dev-workflowWrote 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/andreeved/1c-ai-feature-dev-workflow/1c-feature-dev)<a href="https://agentmods.dev/skills/andreeved/1c-ai-feature-dev-workflow/1c-feature-dev"><img src="https://agentmods.dev/badge/skills/andreeved/1c-ai-feature-dev-workflow/1c-feature-dev/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/andreeved/1c-ai-feature-dev-workflow/1c-feature-dev"><img src="https://agentmods.dev/badge/skills/andreeved/1c-ai-feature-dev-workflow/1c-feature-dev.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.00101 | $0.03647 |
| Opus 5.5 | $0.00040 | $0.01459 |
| Sonnet 5.5 | $0.00020 | $0.00729 |
| Haiku 4.5 | $0.00010 | $0.00365 |
Grade A, and why
1c-feature-dev 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Принципы работы
- Адаптивность: количество агентов и глубина анализа зависят от сложности задачи
- Ранняя валидация: ревью плана до реализации, а не после
- Уточнение требований: выявление всех неоднозначностей до проектирования через вопросы пользователю
- Атомарные шаги: этапы реализации с критериями приемки и проверками
- Отслеживание прогресса: после завершения каждой фазы отмечай её как завершённую в списке задач
Phase 0: Инициализация и оценка сложности
Цель: понять масштаб задачи и создать структуру для работы
Начальный запрос: $ARGUMENTS
Действия:
- Создай список задач со всеми фазами
- Создай директорию
.tasks/task-[feature-name]/для хранения артефактов - Оцени сложность задачи (простая/средняя/сложная/критичная):
- Простая: небольшое изменение, очевидная реализация
- Средняя: затрагивает несколько модулей, требует понимания архитектуры
- Сложная: большая доработка, несколько подсистем, неочевидные решения
- Критичная: архитектурные изменения, влияние на всю систему, высокие риски
- Запиши оценку сложности в файл
.tasks/task-[feature-name]/phase0-complexity.md
Phase 1: Discovery
Цель: понять, что нужно построить
Действия:
- Если доработка неясна, спроси пользователя:
- Какую проблему они решают?
- Что должна делать доработка?
- Есть ли ограничения или требования?
- Резюмируй понимание и получи подтверждение от пользователя
- Сохрани подтвержденное понимание в файл
.tasks/task-[feature-name]/phase1-requirements.md:- Исходный запрос из $ARGUMENTS
- Уточняющие вопросы и ответы (если были)
- Резюме понимания задачи
- Ключевые требования и ограничения
- Подтверждение пользователя
Phase 2: Исследование кодовой базы 1C
Цель: понять существующий код и паттерны
ПРИНЦИПЫ АДАПТИВНОГО ИССЛЕДОВАНИЯ:
ТЫ ПРИНИМАЕШЬ РЕШЕНИЕ о стратегии исследования на основе:
- Оценки сложности из Phase 0
- Характера задачи (новая доработка vs расширение существующей)
- Того, насколько понятна область кодовой базы
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.
- 1mo ago First seen · 275 lines · 101 tokens per session scan A 5d7fd83004cb
1c-feature-dev is a skill published in the GitHub repository AndreevED/1c-ai-feature-dev-workflow (155 stars, last pushed 7mo ago), licensed MIT. It adds 101 tokens to every session and 3,647 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
form-compile
A form generator for managed 1C applications. It creates Form.xml from a JSON description or from an object's 1C metadata, such as a catalogue or document.
form-edit
A tool for modifying an existing managed form in 1C by adding screen elements, fields, commands, and event handlers. Event handlers are code routines that run when something happens, such as a field changing.
skd-edit
A focused editor for 1C data composition schemas, the report definitions that describe queries, fields, filters, totals, and parameters. It changes an existing Template.xml file through specific operations.
db-repo
A command for working with a 1C configuration repository, which stores versions and controls changes to configuration objects.
cfe-borrow
A tool for borrowing existing 1C configuration objects into an extension, so the extension can alter or add to those objects.