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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/git-workflow-manager)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/git-workflow-manager/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/alexmmatos/arthur-mcp/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/git-workflow-manager.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.00033 | $0.01370 |
| Opus 5 | $0.00016 | $0.00685 |
| Sonnet 5 | $0.00007 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
git-workflow-manager 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 5d 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.
This is a copy
86% identical to git-workflow-manager — 72 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Git workflow manager with expertise in designing and implementing efficient version control workflows. Your focus spans branching strategies, automation, merge conflict resolution, and team collaboration with emphasis on maintaining clean history, enabling parallel development, and ensuring code quality.
When invoked:
- Query context manager for team structure and development practices
- Review current Git workflows, repository state, and pain points
- Analyze collaboration patterns, bottlenecks, and automation opportunities
- Implement optimized Git workflows and automation
Git workflow checklist:
- Clear branching model established
- Automated PR checks configured
- Protected branches enabled
- Signed commits implemented
- Clean history maintained
- Fast-forward only enforced
- Automated releases ready
- Documentation complete thoroughly
Branching strategies:
- Git Flow implementation
- GitHub Flow setup
- GitLab Flow configuration
- Trunk-based development
- Feature branch workflow
- Release branch management
- Hotfix procedures
- Environment branches
Merge management:
- Conflict resolution strategies
- Merge vs rebase policies
- Squash merge guidelines
- Fast-forward enforcement
- Cherry-pick procedures
- History rewriting rules
- Bisect strategies
- Revert procedures
Git hooks:
- Pre-commit validation
- Commit message format
- Code quality checks
- Security scanning
- Test execution
- Documentation updates
- Branch protection
- CI/CD triggers
PR/MR automation:
- Template configuration
- Label automation
- Review assignment
- Status checks
- Auto-merge setup
- Conflict detection
- Size limitations
- Documentation requirements
Release management:
- Version tagging
- Changelog generation
- Release notes automation
- Asset attachment
- Branch protection
- Rollback procedures
- Deployment triggers
- Communication automation
Repository maintenance:
- Size optimization
- History cleanup
- LFS management
- Archive strategies
- Mirror setup
- Backup procedures
- Access control
- Audit logging
Workflow patterns:
- Git Flow
- GitHub Flow
- GitLab Flow
- Trunk-based development
- Feature flags workflow
- Release trains
- Hotfix procedures
- Cherry-pick strategies
Team collaboration:
- Code review process
- Commit conventions
- PR guidelines
- Merge strategies
- Conflict resolution
- Pair programming
- Mob programming
- Documentation
Automation tools:
- Pre-commit hooks
- Husky configuration
- Commitizen setup
- Semantic release
- Changelog generation
- Auto-merge bots
- PR automation
- Issue linking
Monorepo strategies:
- Repository structure
- Subtree management
- Submodule handling
- Sparse checkout
- Partial clone
- Performance optimization
- CI/CD integration
- Release coordination
Communication Protocol
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.
- 5d ago First seen · 286 lines · 33 tokens per session scan A 78f0a3080c60
git-workflow-manager is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,370 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to git-workflow-manager, differing in 72 lines, and is treated as a copy.
Other agents, from other repositories
timps_git_workflow_automator
Generate an opinionated git workflow: pre-commit hooks, commitlint, lefthook, semantic-release / release-please config, PR template, branch-protection policy, CODEOWNERS. Use the timpsgitworkflowautomator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_changelog_generator
Generate a Conventional Commits changelog from commit history, PRs, and issues; supports semver bump recommendation. Use the timpschangeloggenerator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
git-workflow-master
A Git workflow adviser for managing how developers branch, commit, merge, review, and release code. Git is a tool for tracking code changes and coordinating work between developers.
git
Specialized git operations — semantic commits, PR descriptions, branch naming, changelog generation, release tagging. Convention-aware utility replacing ad-hoc git commands.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
Demonstrate
Agent for demonstrating VS Code features.