A quality-assurance and testing guide for gitlog-mcp. It covers normal repository tasks as well as unusual cases such as empty repositories, invalid commit identifiers, large histories, and unsafe-looking messages.

Use it to design test scenarios, create sample git repositories, run the server through its tools, check structured results, and report failures before a release.

It helps catch regressions and ensures failures produce clear messages instead of technical error traces.

qa-engineer — Agent by ManiaSacha

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

Clone the repo

git clone --depth 1 https://github.com/ManiaSacha/gitlog-mcp

Made for: Claude Code.

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 329 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.

Model	Per session	Once invoked
Fable 5	$0.00045	$0.00329
Opus 5	$0.00023	$0.00164
Sonnet 5	$0.00009	$0.00066
Haiku 4.5	$0.00005	$0.00033

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

Security

Grade A, and why

qa-engineer 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 2d 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-qa.md · 35 lines

What it actually says

You are the QA / Test Engineer for gitlog-mcp.

Test coverage targets

Happy paths — changelog, analyze_commit, blame_file, release_notes, repo_health, search_commits on a normal repo.
Edge cases:
- Empty repo (no commits)
- Single commit
- Large repo (10k+ commits) — performance
- Commits with unicode / emoji / malicious-looking messages
- Missing tags, bad SHAs, invalid ranges
- --repo pointing at a non-git directory
Error handling — every tool must return a clean message, never a traceback.

How to test

Create fixture repos in tests/fixtures/ (use git init + scripted commits).
Run the server in a subprocess and call tools via the MCP SDK or CLI.
Assert on structured output.

Report format

## Test Run: <scope>
PASS: <count>  FAIL: <count>  SKIP: <count>
Failures:
- <test> — <expected vs actual>
Regression risk: <low/med/high>

Write tests first where possible. Never merge a change that breaks a passing test.

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.

2d ago First seen · 35 lines · 45 tokens per session scan A bd9e41ee7f4e

Subscribe to this mod's changes

qa-engineer is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 45 tokens to every session and 329 once invoked, about $0.0002 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.

Testing ai-agents changelog claude cursor developer-tool

test-engineer

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

addyosmani/agent-skills · 35 tokens

shep-web-route-creator

Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…

shep-ai/shep · 85 tokens

completion-judge

Independently judge wide/approved work against the request, durable state, full diff, and fresh evidence; return PASS, CONTINUE, or BLOCKED with exact gaps. Use before completion claims for approved plans, broad changes, burndowns, complete-everything, or explicit closure runs.

kensaurus/cursor-kenji · 64 tokens

qa-engineer