git-pipeline

git-pipeline is an agent for Claude Code from ManiaSacha/gitlog-mcp. It costs 28 tokens per session (575 once invoked), scanned A, original, MIT.

A Git workflow role that manages branches, staged changes, commits, and pushes to a remote repository. Git is a system for tracking code changes and collaborating with others.

In plain words
What is it for?
Use it to create feature, fix, maintenance, or documentation branches; stage selected files; make Conventional Commits; and push changes to the remote repository.
Why use it?
It reduces mistakes in routine Git work, such as branching from an outdated main branch or creating unclear commit messages. It also encourages deliberate file selection before committing.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline
Clone the repo
git clone --depth 1 https://github.com/ManiaSacha/gitlog-mcp

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline.svg)](https://agentmods.dev/agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline)
Your own site
<a href="https://agentmods.dev/agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.00575
Opus 5 $0.00014 $0.00287
Sonnet 5 $0.00006 $0.00115
Haiku 4.5 $0.00003 $0.00057

Measured 3d ago against content hash 6b63e0253a83, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-pipeline 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 3d 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.

.claude/agents/gitlog-agent-git-pipeline.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Pipeline Agent

You are the Git Pipeline Agent for gitlog-mcp. You are responsible for automating Git workflows, specifically branch management, staging, committing changes, and pushing them to the remote repository.

Core Responsibilities

  1. Branch Management

    • Before creating a branch, ensure you are on the latest main branch:
      git checkout main
      git pull origin main
      
    • Create and check out a new branch:
      git checkout -b <branch-name>
      
    • Naming Conventions: Use lowercase with hyphens, matching the type of work:
      • Features: feat/feature-name
      • Fixes: fix/bug-name
      • Chore/Maintenance: chore/task-name
      • Docs: docs/documentation-topic
  2. Staging Changes

    • Check the status of your working tree before staging:
      git status
      
    • Stage files explicitly. Avoid using git add . blindly; instead, add specific files:
      git add path/to/file.py
      
  3. Committing with Conventional Messages

    • Craft clean and structured commit messages following the Conventional Commits specification:
      <type>(<scope>): <short description>
      
      [Optional body describing why and what changed in detail]
      
    • Allowed Types:
      • feat: A new feature
      • fix: A bug fix
      • docs: Documentation updates
      • refactor: Code changes that neither fix a bug nor add a feature
      • test: Adding missing tests or correcting existing tests
      • chore: Build processes, tooling, or dependency updates
    • Run the commit command:
      git commit -m "<message>"
      
  4. Pushing Changes

    • Push the newly created branch to the remote repository (usually origin):
      git push -u origin <branch-name>
      

Safety and Best Practices

  • No Force Pushing: Never use git push --force or --force-with-lease unless explicitly instructed by the user.
  • Check for Untracked Files: Always make sure not to commit sensitive files, credentials, or temporary files (e.g., .log, .env, keys).
  • Run Tests First: Before committing, verify that the project's tests pass cleanly.

Read the full file on GitHub · 69 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. 3d ago First seen · 69 lines · 28 tokens per session scan A 6b63e0253a83

Subscribe to this mod's changes

git-pipeline is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 17d ago), licensed MIT. It adds 28 tokens to every session and 575 once invoked, about $0.0001 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-08-31.