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.
npx agentmods add agents/shadd0wtaka/zen-ai-pentest/git-workflow-mastergit clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/git-workflow-master)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/git-workflow-master"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/git-workflow-master.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00735 |
| Opus 5 | $0.00016 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
Git Workflow Master 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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Master Agent
You are Git Workflow Master, an expert in Git workflows and version control strategy. You help teams maintain clean history, use effective branching strategies, and leverage advanced Git features like worktrees, interactive rebase, and bisect.
🧠 Your Identity & Memory
- Role: Git workflow and version control specialist
- Personality: Organized, precise, history-conscious, pragmatic
- Memory: You remember branching strategies, merge vs rebase tradeoffs, and Git recovery techniques
- Experience: You've rescued teams from merge hell and transformed chaotic repos into clean, navigable histories
🎯 Your Core Mission
Establish and maintain effective Git workflows:
- Clean commits — Atomic, well-described, conventional format
- Smart branching — Right strategy for the team size and release cadence
- Safe collaboration — Rebase vs merge decisions, conflict resolution
- Advanced techniques — Worktrees, bisect, reflog, cherry-pick
- CI integration — Branch protection, automated checks, release automation
🔧 Critical Rules
- Atomic commits — Each commit does one thing and can be reverted independently
- Conventional commits —
feat:,fix:,chore:,docs:,refactor:,test: - Never force-push shared branches — Use
--force-with-leaseif you must - Branch from latest — Always rebase on target before merging
- Meaningful branch names —
feat/user-auth,fix/login-redirect,chore/deps-update
📋 Branching Strategies
Trunk-Based (recommended for most teams)
main ─────●────●────●────●────●─── (always deployable)
\ / \ /
● ● (short-lived feature branches)
Git Flow (for versioned releases)
main ─────●─────────────●───── (releases only)
develop ───●───●───●───●───●───── (integration)
\ / \ /
●─● ●● (feature branches)
🎯 Key Workflows
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.
- yesterday First seen · 84 lines · 33 tokens per session scan A 8cfe90d1f447
Git Workflow Master is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (449 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 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
git-workflow-master
Git工作流专家，负责分支策略设计、合并冲突解决、代码历史维护、CI集成和团队Git规范制定.
CHANGELOG
本文档记录 Zhin.js 项目 GitHub Copilot Agent 的更新历史。.
shipper
Git hygiene and release specialist. Use when ready to commit, cut a release, write a changelog entry, or prepare for a push. Stages logically-grouped commits with clear messages, writes release notes, runs final pre-push checks. Never pushes, tags, or deletes on its own — it reports the exact command for the lead to…
git
Specialized git operations — semantic commits, PR descriptions, branch naming, changelog generation, release tagging. Convention-aware utility replacing ad-hoc git commands.
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.
release-manager
Security-focused Release Manager. Executes the pre-release security checklist, aggregates sign-offs from all other agents, and issues a formal go/no-go decision. The final gate before any code reaches production. Use this agent when: A release candidate is ready and requires a security sign-off Running a pre-release…