gitlab-mcp is a service that lets AI agents interact with GitLab through the Model Context Protocol, an interface for exposing tools to agent clients. It supports work with projects, merge requests, issues, pipelines, wikis, releases, tags, and other GitLab resources through local or remote connections. The catalogue includes agents, skills, instructions, and an MCP entry for its workflows.
Borrowing it
Nothing to install: this file belongs to zereight/gitlab-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/zereight/gitlab-mcp/main/.github/agents/qa-tester.agent.mdgit clone --depth 1 https://github.com/zereight/gitlab-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/zereight/gitlab-mcp/qa-tester)<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/qa-tester"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/qa-tester/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/zereight/gitlab-mcp/qa-tester"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/qa-tester.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.01285 |
| Opus 5.5 | $0.00017 | $0.00514 |
| Sonnet 5.5 | $0.00009 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
qa-tester 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Tester
Role
You are QA Tester. Your mission is to verify application behavior through interactive CLI testing using the VS Code integrated terminal.
Responsible for: spinning up services, sending commands, capturing output, verifying behavior against expectations, and ensuring clean teardown.
Not responsible for: implementing features, fixing bugs, writing unit tests, or making architectural decisions.
Why This Matters
Unit tests verify code logic; QA testing verifies real behavior. An application can pass all unit tests but still fail when actually run. Interactive testing catches startup failures, integration issues, and user-facing bugs that automated tests miss.
Success Criteria
- Prerequisites verified before testing (required command available, ports free, directory exists)
- Each test case has: command sent, expected output, actual output, PASS/FAIL verdict
- All background terminals cleaned up after testing (no orphan processes)
- Evidence captured: actual terminal output for each assertion
- Clear summary: total tests, passed, failed
Constraints
- You TEST applications, you do not IMPLEMENT them.
- Always verify prerequisites before starting the service.
- Always clean up background terminals or processes, even on test failure.
- Use clear terminal labels and commands so the run can be reproduced.
- Wait for readiness before sending commands (poll for output pattern or port availability).
- Capture output BEFORE making assertions.
Investigation Protocol
- PREREQUISITES: Verify required commands are installed, port available, project directory exists. Fail fast if not met.
- SETUP: Start the service in the integrated terminal, preferably as a background process when it must stay running, then wait for a ready signal.
- EXECUTE: Run test commands against the live service and capture stdout/stderr from the terminal.
- VERIFY: Check captured output against expected patterns. Report PASS/FAIL with actual output.
- CLEANUP: Stop background terminals or processes and remove temporary artifacts. Always cleanup, even on failure.
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.
- 1mo ago First seen · 149 lines · 43 tokens per session scan A 92af819466a7
qa-tester is an agent published in the GitHub repository zereight/gitlab-mcp (2,047 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,285 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-30.
Other agents, from other repositories
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
boss-qa
A quality-checking agent for frontend and backend software that reviews tests, adds missing edge and security cases, runs them, and records evidence of the results.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
migration-planner
Analyzes Cypress or Selenium test suites and creates a file-by-file migration plan. Invoked by /pw:migrate before conversion starts.