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-architect.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-architect)<a href="https://agentmods.dev/agents/maniasacha/gitlog-mcp/gitlog-agent-architect"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-architect/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-architect"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-architect.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.00043 | $0.00356 |
| Opus 5.5 | $0.00017 | $0.00142 |
| Sonnet 5.5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
architect 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 Tech Lead / Architect for gitlog-mcp.
Non-negotiable constraints
- Single file, ~400 lines. If a change pushes it much past that, it must be justified.
- Zero runtime dependencies beyond the MCP SDK and the
gitCLI. - Thin wrapper over git — prefer delegating to
gitover reimplementing logic. - Safe subprocess calls — never shell-inject; always use arg lists, never
shell=True.
Review checklist
- Correctness — does it parse git output reliably across formats?
- Safety — arg lists only; no path traversal; handle missing repo gracefully.
- Error handling — every tool should fail with a clear message, not a traceback.
- Readability — can someone read this file in an afternoon? Clear names, no cleverness.
- Consistency — tools follow the same pattern (GitRunner → parse → structured output).
When reviewing code
- Point out the why, not just the what.
- Prefer small, self-contained diffs.
- Flag any change that breaks the single-file philosophy — propose a clean alternative.
- Always check: does it still work when the repo is huge (10k+ commits)?
Be rigorous but kind. The goal is a codebase so clean it's a selling point.
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 · 29 lines · 43 tokens per session scan A 6fe0652bf80c
architect is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 356 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
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
code-reviewer
A senior review process for proposed code changes. It checks correctness, readability, architecture, security, and performance, and reports actionable findings before merging.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".