Zen-Ai-Pentest: Agent for Claude Code

.opencode/agents/git-workflow-master.md

Git Workflow Master is an agent for Claude Code, OpenCode from SHAdd0WTAka/Zen-Ai-Pentest. It costs 33 tokens per session (735 once invoked), scanned A, original, MIT.

A Git workflow specialist for organizing code changes, branches, merges, rebases, worktrees, and releases. Git is a system for tracking source-code history and coordinating changes between developers.

In plain words
What is it for?
Use it to choose branching strategies, write focused conventional commits, resolve conflicts, use advanced Git recovery tools, and connect workflows to CI and release automation.
Why use it?
It helps teams avoid confusing histories, risky merges, unclear commits, and branch practices that interfere with automated checks or releases.

Agent for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

This is SHAdd0WTAka/Zen-Ai-Pentest's own configuration. It tells Claude Code and OpenCode how to work on Zen-Ai-Pentest itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Zen-Ai-Pentest configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SHAdd0WTAka/Zen-Ai-Pentest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SHAdd0WTAka/Zen-Ai-Pentest/main/.opencode/agents/git-workflow-master.md
Clone the repo
git clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-Pentest

Made for: Claude Code, OpenCode.

Wrote 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.

agentmods badge for Git Workflow Master

README.md
[![agentmods](https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/git-workflow-master/github.svg)](https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/git-workflow-master)
Your own site
<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/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.

agentmods 80×15 button for Git Workflow Master

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00735
Opus 5.5 $0.00013 $0.00294
Sonnet 5.5 $0.00007 $0.00147
Haiku 4.5 $0.00003 $0.00073

Measured 1mo ago against content hash 8cfe90d1f447, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.opencode/agents/git-workflow-master.md · 84 lines

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:

  1. Clean commits — Atomic, well-described, conventional format
  2. Smart branching — Right strategy for the team size and release cadence
  3. Safe collaboration — Rebase vs merge decisions, conflict resolution
  4. Advanced techniques — Worktrees, bisect, reflog, cherry-pick
  5. CI integration — Branch protection, automated checks, release automation

🔧 Critical Rules

  1. Atomic commits — Each commit does one thing and can be reverted independently
  2. Conventional commits — feat:, fix:, chore:, docs:, refactor:, test:
  3. Never force-push shared branches — Use --force-with-lease if you must
  4. Branch from latest — Always rebase on target before merging
  5. 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

Read the full file on GitHub · 84 lines

Changes

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.

  1. 1mo ago First seen · 84 lines · 33 tokens per session scan A 8cfe90d1f447

Subscribe to this mod's changes

Git Workflow Master is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (499 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 735 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.