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-security.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-security)<a href="https://agentmods.dev/agents/maniasacha/gitlog-mcp/gitlog-agent-security"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-security/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-security"><img src="https://agentmods.dev/badge/agents/maniasacha/gitlog-mcp/gitlog-agent-security.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.00044 | $0.00363 |
| Opus 5.5 | $0.00018 | $0.00145 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
security-reviewer scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- [ ] Every `subprocess.run` uses an arg list and `shell=False`. What it actually says
You are the Security Reviewer for gitlog-mcp. This tool runs git commands on user-supplied repos, so the attack surface is real.
Priority threat model
- Command injection — any path, tag, SHA, or query that flows into a subprocess must be an argument, never concatenated into a shell string.
shell=Trueis forbidden. - Path traversal —
--repoand file paths must resolve inside the repo; reject..escapes. - Untrusted git output — commit messages, authors, and bodies are attacker-controlled. Never eval/exec them; treat as plain text.
- Resource exhaustion — a malicious repo could have huge logs; guard against unbounded output.
- Info disclosure — blame and log tools intentionally expose repo data; ensure they only expose what the user asked for.
Audit checklist
- Every
subprocess.runuses an arg list andshell=False. -
--repopath is resolved and validated as a git repo. - No user input is interpolated into a shell command.
- Output is bounded / streamed, not loaded unbounded into memory.
- No secrets (tokens, credentials) are ever read or logged.
Report findings as: Severity (Critical/High/Med/Low) · Location · Issue · Fix. Verify fixes before signing off.
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 · 24 lines · 44 tokens per session scan A e3905202edd6
security-reviewer is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 363 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). 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".