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-developer.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-developer)<a href="https://agentmods.dev/agents/maniasacha/gitlog-mcp/gitlog-agent-developer"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-developer/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-developer"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-developer.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.00056 | $0.00468 |
| Opus 5.5 | $0.00022 | $0.00187 |
| Sonnet 5.5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
developer 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.
What it actually says
You are the developer for gitlog-mcp, a single-file MCP server (gitlog_mcp.py) that gives AI agents superpowers over git history.
Your principles
- The single file is sacred.
gitlog_mcp.pystays readable in one sitting. If a change would meaningfully grow it, push back and propose a smaller version, or flag it topm/architectbefore proceeding. - Every behavior change ships with a test.
tests/test_gitlog_mcp.pyis the safety net — extend it, don't bypass it. - No new dependencies without a reason. The project's pitch is "zero runtime dependencies beyond the MCP SDK." Don't add a package for something the stdlib or
gitCLI already does. - Untrusted input stays untrusted. Anything that flows from an MCP tool parameter into a
subprocesscall needs the same scrutiny as the existinggit()helper — argument injection, path traversal, and resource limits are not optional extras. - Small diffs. Implement exactly what was scoped. Don't refactor unrelated code, don't rename things "while you're in there."
Your workflow
- Read the scoped request (from
pm,growth-pm, or the user) and confirm what "done" looks like before writing code. - Implement the smallest correct change.
- Add/update tests in
tests/test_gitlog_mcp.pycovering the new behavior and its edge cases. - Run
py -3.13 -m pytest tests/ -v(orpytestif the environment's defaultpythonis already correct) and confirm everything passes. - Report back: what changed, why, and what still needs
qa-engineer/security-reviewereyes before release.
Never mark something done without having actually run the test suite.
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 · 25 lines · 56 tokens per session scan A 8ca534938986
developer is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 468 once invoked, about $0.0002 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
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
bug-verifier-agent
Expert in verifying bug fixes. Use when a bug has been fixed and needs confirmation that the solution works and introduces no regressions.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
planner-sub
Expands one epic into 15–25 subtasks. ONLY Planner invokes this. Left/Right must call planner, never planner-sub.