Borrowing it
Nothing to install: this file belongs to radif-ru/ai-multi-agent-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/radif-ru/ai-multi-agent-system/main/.agents/skills/git-discipline/SKILL.mdgit clone --depth 1 https://github.com/radif-ru/ai-multi-agent-systemWrote 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/radif-ru/ai-multi-agent-system/git-discipline)<a href="https://agentmods.dev/skills/radif-ru/ai-multi-agent-system/git-discipline"><img src="https://agentmods.dev/badge/skills/radif-ru/ai-multi-agent-system/git-discipline/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/radif-ru/ai-multi-agent-system/git-discipline"><img src="https://agentmods.dev/badge/skills/radif-ru/ai-multi-agent-system/git-discipline.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.00050 | $0.00970 |
| Opus 5.5 | $0.00020 | $0.00388 |
| Sonnet 5.5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
git-discipline 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: git-discipline
Правила работы с git. Источник истины — _docs/instructions.md §2 и _board/process.md §7.
Когда использовать
- Начинаешь/закрываешь задачу спринта.
- Готовишь любой коммит.
- Настраиваешь ветку под спринт.
Алгоритм
- Ветки. Основная —
main, рабочие —feature/<NN>-<short-name>(по одной на спринт, отmain). - Коммиты — атомарные, в императиве, по Conventional Commits. Текст — на русском, идентификаторы — латиницей.
feat(handlers): добавить команду /newfix(memory): обработать недоступность sqlite-vec при стартеtest(tools): покрыть calculator случаем деления на нольdocs(architecture): уточнить поток /new в §5
- Ритуал задачи (трёхэтапный). ID в сообщении —
<NN>.<stage>.<task>, где<NN>— двузначный номер спринта (_board/process.md§3 п.3):- Начать:
python3 -m scripts.task start <NN>.<stage>.<task>. - Код/доки: атомарные коммиты содержимого (
feat/fix/docs/test/...). - Закрыть:
python3 -m scripts.task done <NN>.<stage>.<task> --note "<что сделано>". Скрипт сам меняет статус в заголовке задачи и сводной таблице, проставляет чекбоксы DoD, дописывает историю спринта, пересчитывает счётчикиplan.md, прогоняетcheck_sprint_syncи коммитит оба файла. Править эти места руками не нужно; DoD должен быть фактически выполнен доdone.
- Начать:
- Перед каждым кодовым коммитом (кроме
chore(plan): ...) — одна команда, зелёная:bash .agents/skills/git-discipline/scripts/preflight.sh(артефакты,flake8,pytestс порогом покрытия, все скрипты-гейты — список в_board/process.md§7.10). Если что-то красное (даже не относящееся к задаче) — сначала чинится. Отдельныеpytest -q/flake8 app tests— только для точечной проверки по ходу работы. - Коммит вне спринта (активного спринта нет, правка ≤ S или доки) — через журнал: запись в
_board/maintenance.mdтем же коммитом, что и правка (_board/process.md§12). Новая функциональность и правки > S — только спринтом. .gitignoreобязан содержать:.env,.venv/,__pycache__/,*.pyc,logs/,data/,*.db,.pytest_cache/,.idea/,.vscode/.
What ships with it
1 file 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.
- 1mo ago First seen · 44 lines · 50 tokens per session scan A dace13a2d0ac
git-discipline is a skill published in the GitHub repository radif-ru/ai-multi-agent-system (6 stars, last pushed 21d ago), licensed MIT. It adds 50 tokens to every session and 970 once invoked, about $0.0002 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-31.
Other skills, from other repositories
working-in-turns
Keep each turn bounded, checkpointed, and reviewable.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.
pr-authoring
Playbook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.
pr-review
Playbook for reviewing pull requests — verdict format, verification-not-trust, severity-ranked findings with concrete fixes, risk acceptance on the record. The reviewer-side counterpart of pr-authoring.