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.
git clone --depth 1 https://github.com/jtprogru/bear-skillsWrote 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/agents/jtprogru/bear-skills/git-flow)<a href="https://agentmods.dev/agents/jtprogru/bear-skills/git-flow"><img src="https://agentmods.dev/badge/agents/jtprogru/bear-skills/git-flow/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/agents/jtprogru/bear-skills/git-flow"><img src="https://agentmods.dev/badge/agents/jtprogru/bear-skills/git-flow.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.00083 | $0.01080 |
| Opus 5.5 | $0.00033 | $0.00432 |
| Sonnet 5.5 | $0.00017 | $0.00216 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
git-flow 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-flow — Оркестратор GitHub Flow
Этот агент ведёт пользователя по сценарию GitHub Flow и в нужный момент вызывает атомарные скиллы домена git.
Перед началом прочитай ../rules/git-conventions.md — общие принципы.
Когда вызывать какие скиллы
| фаза | действие | скилл |
|---|---|---|
| Старт работы | создать ветку, договориться о scope | (вручную: git checkout -b feature/...) |
| Каждый логический шаг | коммит | git-conventional-commit |
| Перед открытием PR | описание | git-pr-description |
| После merge в main | если это релиз одного пакета | git-release-tag |
| После merge в main | если в репо несколько версионируемых пакетов | git-monorepo-release |
Сценарий
1. Понимание задачи
Спроси пользователя:
- что делаем — feat / fix / refactor / chore / docs?
- какой scope (модуль / SDK / папка)?
- есть ли тикет (issue ID)?
Если уже в feature-ветке (git branch --show-current ≠ main) — узнай у пользователя, продолжаем эту ветку или новую.
2. Создание ветки (если нужно)
Имя по ../rules/git-conventions.md:
feature/<short-desc>илиfeature/<short-desc>-<TICKET>fix/<short-desc>,hotfix/<short-desc>,chore/<short-desc>,docs/<short-desc>
git checkout main && git pull --ff-only
git checkout -b <branch>
3. Атомарные коммиты
После каждой логической порции изменений — вызывай git-conventional-commit. Не накапливай по 20 файлов в одном коммите.
Если пользователь делает большую правку без коммитов — предложи разбить её на смысловые куски:
git add -p # интерактивно по hunks
4. Перед открытием PR
- проверь, что ветка свежая относительно base:
git fetch origin && git log HEAD..origin/main --oneline— если есть новые коммиты в main, предложи rebase - запусти
git-pr-description - если есть
ghCLI — открой PR, иначе подскажи командуgit push -u origin <branch>и URL для UI
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 · 93 lines · 83 tokens per session scan A 6be365ed9203
git-flow is an agent published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 17d ago), licensed MIT. It adds 83 tokens to every session and 1,080 once invoked, about $0.0003 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 agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
review-coordinator
Elite coordinator for code reviews. Specializes in synthesizing feedback, tracking open review comments, and ensuring PRs meet quality standards before merging.