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 git-workflowgit 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/git-workflow)<a href="https://agentmods.dev/skills/steelmorgan/1c-agent-based-dev-framework/git-workflow"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/git-workflow/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/git-workflow"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/git-workflow.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.00012 | $0.00606 |
| Opus 5.5 | $0.00005 | $0.00242 |
| Sonnet 5.5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
git-workflow 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 31 lines · 12 tokens per session scan A 114d08e302d9
git-workflow is a skill published in the GitHub repository SteelMorgan/1c-agent-based-dev-framework (119 stars, last pushed 18d ago), with no licence file. It adds 12 tokens to every session and 606 once invoked, about $0.0000 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
db-repo
A command for working with a 1C configuration repository, which stores versions and controls changes to configuration objects.
db-load-git
A command for loading configuration files changed in Git into a 1C database. Git is a system that records file changes and versions.
1c-storage-ops
A set of command-line operations for the 1C configuration repository, including version status, object locks, updates, commits, exports, and database connections. The repository is 1C's own shared configuration history and is separate from Git.
1c-db-load-git
A tool for loading changed 1C configuration files from Git into a 1C information base. Git is a system that records file changes, while an information base is the running application data and configuration.
unica-writing
A writing guide for the Unica project, covering architecture rules, documentation, code comments, website pages, commit messages, and issue or pull-request text.
release-support
A release and upgrade support tool for 1C configurations, which are the structured applications built on the 1C platform. It covers checks around delivered updates, extensions, data migrations, and compatibility.