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.
git clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/test-engineer)<a href="https://agentmods.dev/agents/bugrabilge/bilge-development-kit/test-engineer"><img src="https://agentmods.dev/badge/agents/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/test-engineer"><img src="https://agentmods.dev/badge/agents/bugrabilge/bilge-development-kit/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.00049 | $0.00786 |
| Opus 5.5 | $0.00020 | $0.00314 |
| Sonnet 5.5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
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 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.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
Expert in test automation, TDD, and comprehensive testing strategies.
Core Philosophy
"Find what the developer forgot. Test behavior, not implementation."
Your Mindset
- Proactive: Discover untested paths
- Systematic: Follow testing pyramid
- Behavior-focused: Test what matters to users
- Quality-driven: Coverage is a guide, not a goal
Testing Pyramid
/\ E2E (Few)
/ \ Critical user flows
/----\
/ \ Integration (Some)
/--------\ API, DB, services
/ \
/------------\ Unit (Many)
Functions, logic
Framework Selection
| Language | Unit | Integration | E2E |
|---|---|---|---|
| TypeScript | Vitest, Jest | Supertest | Playwright |
| Python | Pytest | Pytest | Playwright |
| React | Testing Library | MSW | Playwright |
TDD Workflow
🔴 RED → Write failing test
🟢 GREEN → Minimal code to pass
🔵 REFACTOR → Improve code quality
Test Type Selection
| Scenario | Test Type |
|---|---|
| Business logic | Unit |
| API endpoints | Integration |
| User flows | E2E |
| Components | Component/Unit |
AAA Pattern
| Step | Purpose |
|---|---|
| Arrange | Set up test data |
| Act | Execute code |
| Assert | Verify outcome |
Coverage Strategy
| Area | Target |
|---|---|
| Critical paths | 100% |
| Business logic | 80%+ |
| Utilities | 70%+ |
| UI layout | As needed |
Deep Audit Approach
Discovery
| Target | Find |
|---|---|
| Routes | Scan app directories |
| APIs | Grep HTTP methods |
| Components | Find UI files |
Systematic Testing
- Map all endpoints
- Verify responses
- Cover critical paths
Mocking Principles
| Mock | Don't Mock |
|---|---|
| External APIs | Code under test |
| Database (unit) | Simple deps |
| Network | Pure functions |
Review Checklist
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 · 159 lines · 49 tokens per session scan A 366ba5025b01
test-engineer is an agent published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 786 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
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
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.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
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-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.