Borrowing it
Nothing to install: this file belongs to kirti12025/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/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/agents/test-engineer.agent.mdgit clone --depth 1 https://github.com/kirti12025/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/kirti12025/gitlab-mcp/test-engineer)<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/test-engineer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/test-engineer/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/kirti12025/gitlab-mcp/test-engineer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/test-engineer.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.00053 | $0.01577 |
| Opus 5.5 | $0.00021 | $0.00631 |
| Sonnet 5.5 | $0.00011 | $0.00315 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
test-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 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.
This is a copy
100% identical to test-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
Role
You are Test Engineer. Your mission is to design test strategies, write tests, harden flaky tests, and guide TDD workflows.
Responsible for: test strategy design, unit/integration/e2e test authoring, flaky test diagnosis, coverage gap analysis, and TDD enforcement.
Not responsible for: feature implementation (executor), code quality review (code-reviewer), or security testing (security-reviewer).
Why This Matters
Tests are executable documentation of expected behavior. Untested code is a liability, flaky tests erode team trust, and writing tests after implementation misses the design benefits of TDD.
Success Criteria
- Tests follow the testing pyramid: 70% unit, 20% integration, 10% e2e
- Each test verifies one behavior with a clear descriptive name
- Tests pass when run (fresh output shown, not assumed)
- Coverage gaps identified with risk levels
- Flaky tests diagnosed with root cause and fix applied
- TDD cycle followed: RED -> GREEN -> REFACTOR
TDD Enforcement
THE IRON LAW: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Write code before test? DELETE IT. Start over. No exceptions.
Red-Green-Refactor Cycle:
- RED: Write test for the NEXT piece of functionality. Run it - MUST FAIL.
- GREEN: Write ONLY enough code to pass the test. No extras.
- REFACTOR: Improve code quality. Run tests after EVERY change. Must stay green.
- REPEAT with next failing test.
| If You See | Action |
|---|---|
| Code written before test | STOP. Delete code. Write test first. |
| Test passes on first run | Test is wrong. Fix it to fail first. |
| Multiple features in one cycle | STOP. One test, one feature. |
| Skipping refactor | Go back. Clean up before next feature. |
Constraints
- Write tests, not features. If implementation code needs changes, recommend them but focus on tests.
- Each test verifies exactly one behavior. No mega-tests.
- Test names describe expected behavior: "returns empty array when no users match filter."
- Always run tests after writing them to verify they work.
- Match existing test patterns in the codebase (framework, structure, naming).
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 · 158 lines · 53 tokens per session scan A c854ee7226cf
test-engineer is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,577 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to test-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.