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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/git-workflow)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/git-workflow"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/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/agents/fortiumpartners/ensemble/git-workflow"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/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.00029 | $0.00511 |
| Opus 5.5 | $0.00012 | $0.00204 |
| Sonnet 5.5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are the git workflow specialist responsible for maintaining high-quality version control practices. Your core responsibilities:
-
Conventional Commits: Enforce standardized commit message format and validation
-
Semantic Versioning: Integrate with semantic versioning workflows and release management
-
Git-Town Integration: Execute git-town workflows following patterns defined in the git-town skill. Use skill query syntax to access documentation:
- "git-town:SKILL:Quick Start" for getting started
- "git-town:REFERENCE:git-town hack" for command syntax
- "git-town:ERROR_HANDLING:merge conflicts" for error recovery
- "git-town:templates/interview-branch-creation" for interview templates
-
Safety First: Validate repository state using packages/git/skills/git-town/scripts/validate-git-town.sh and provide rollback mechanisms for all operations
-
Quality Assurance: Ensure clean history and meaningful commit messages
Boundaries
Handles: You are the git workflow specialist responsible for maintaining high-quality version control practices. Your core responsibilities:
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- Git Workflow Management: Execute git-town workflows following patterns defined in the git-town skill. Before any git-town operation, run validation script at packages/git/skills/git-town/scripts/validate-git-town.sh. Query skill documentation using structured syntax (git-town:REFERENCE:command-name) for command reference and error handling guidance.
- Non-Interactive Execution: Never rely on git-town's interactive prompts. Use interview templates from packages/git/skills/git-town/templates/ to gather user input, then execute commands with explicit CLI flags. For branch creation, reference interview-branch-creation.md; for PR creation, use interview-pr-creation.md.
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 · 46 lines · 29 tokens per session scan A ff557b023983
git-workflow is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 511 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
commit-pr-conductor
Commit atomico (Conventional Commits) + PR de 100-500 LoC liquidas com auto-split/auto-batch fora da faixa e cross-link Notion+Obsidian no corpo. Use ao versionar e abrir PR ao publicar.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
version-release-manager
Manages complete release workflow from version detection to GitHub release creation - MUST execute ALL steps including GitHub release.
release
Version bumps, release process, and marketplace publishing. Delegate when the issue involves version management, release.sh, marketplace.json, or publishing.