Borrowing it
Nothing to install: this file belongs to ManiaSacha/gitlog-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ManiaSacha/gitlog-mcp/main/.claude/agents/gitlog-agent-git-pipeline.mdgit clone --depth 1 https://github.com/ManiaSacha/gitlog-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/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline)<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/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/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-git-pipeline.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.00028 | $0.00575 |
| Opus 5.5 | $0.00011 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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 2mo 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 — 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
-
Branch Management
- Before creating a branch, ensure you are on the latest
mainbranch: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
- Features:
- Before creating a branch, ensure you are on the latest
-
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
- Check the status of your working tree before staging:
-
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 featurefix: A bug fixdocs: Documentation updatesrefactor: Code changes that neither fix a bug nor add a featuretest: Adding missing tests or correcting existing testschore: Build processes, tooling, or dependency updates
- Run the commit command:
git commit -m "<message>"
- Craft clean and structured commit messages following the Conventional Commits specification:
-
Pushing Changes
- Push the newly created branch to the remote repository (usually
origin):git push -u origin <branch-name>
- Push the newly created branch to the remote repository (usually
Safety and Best Practices
- No Force Pushing: Never use
git push --forceor--force-with-leaseunless 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.
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.
- 2mo ago First seen · 69 lines · 28 tokens per session scan A 6b63e0253a83
git-pipeline is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 575 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-08-31.
Other agents, from other repositories
debugging-toolkit-dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
commit-creator
Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit…
pr-creator
Use this agent when asked to create a pull request from staged or committed changes. Read the complete branch diff, carry over relevant findings and verified results, and write a concise body showing the problem and final behavior.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
aif-git-manager
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
learnship-executor
Executes a single learnship PLAN.md atomically — one task at a time with per-task commits, deviation handling, and SUMMARY.md creation. Spawned by execute-phase on platforms with subagent support.