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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/git-expert)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/git-expert"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/git-expert/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/armanzeroeight/fastagent-plugins/git-expert"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/git-expert.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.00034 | $0.01747 |
| Opus 5.5 | $0.00014 | $0.00699 |
| Sonnet 5.5 | $0.00007 | $0.00349 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
git-expert 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Expert
Strategic git workflow decisions and branch management guidance.
Decision Framework
Workflow Selection
Gitflow - When to use:
- Large teams with scheduled releases
- Multiple versions in production
- Need for hotfix support
- Formal release process
Trunk-Based Development - When to use:
- Small to medium teams
- Continuous deployment
- Fast iteration cycles
- Feature flags available
GitHub Flow - When to use:
- Web applications with continuous deployment
- Simple, streamlined process needed
- Single production version
- Pull request-based workflow
GitLab Flow - When to use:
- Environment-based deployments
- Need for staging environments
- Release branches for versions
- Hybrid approach desired
Branching Strategy
Branch Naming Conventions:
feature/description- New featuresbugfix/description- Bug fixeshotfix/description- Production hotfixesrelease/version- Release preparationchore/description- Maintenance tasks
Branch Lifetime:
- Feature branches: Short-lived (1-3 days)
- Release branches: Medium-lived (1-2 weeks)
- Hotfix branches: Very short-lived (hours)
- Main/master: Permanent
- Develop: Permanent (if using Gitflow)
Merge Strategy
Fast-Forward Merge - When to use:
- Linear history desired
- No merge commits wanted
- Simple feature branches
- Clean history priority
Merge Commit - When to use:
- Preserve branch history
- Track feature completion
- Multiple commits in feature
- Audit trail needed
Squash and Merge - When to use:
- Clean main branch history
- Multiple WIP commits
- Single logical change
- Simplified history desired
Rebase and Merge - When to use:
- Linear history required
- No merge commits
- Clean commit history
- Team comfortable with rebasing
Skill Delegation
For commit messages: Delegate to commit-message-generator skill
- Generates conventional commit messages
- Analyzes git diffs
- Follows commit standards
For branching advice: Delegate to branch-strategy-advisor skill
- Recommends branching approaches
- Provides workflow guidance
- Suggests naming conventions
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 · 329 lines · 34 tokens per session scan A 511ea6f27f03
git-expert is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,747 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
deployer
Use for deployment automation, release management, rollouts, and production deployments.
review-coordinator
Elite coordinator for code reviews. Specializes in synthesizing feedback, tracking open review comments, and ensuring PRs meet quality standards before merging.
release-readiness-reviewer
Orchestrates final release readiness checks. Use PROACTIVELY when cutting a release to ensure changelogs, version bumps, and final tests align.
opensource-forker
Fork any project for open-sourcing. Copies files, strips secrets and credentials (20+ patterns), replaces internal references with placeholders, generates .env.example, and cleans git history. First stage of the opensource-pipeline skill.
opensource-packager
Generate complete open-source packaging for a sanitized project. Produces CLAUDE.md, setup.sh, README.md, LICENSE, CONTRIBUTING.md, and GitHub issue templates. Makes any repo immediately usable with Claude Code. Third stage of the opensource-pipeline skill.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.