test-engineer

test-engineer is an agent for coding agents from desilokesh1/antigravity-fullstack-hq. It costs 31 tokens per session (382 once invoked), scanned A, original, MIT.

A software testing adviser covering small code tests, tests between connected parts, and end-to-end tests that follow real user journeys. It also explains test-driven development (TDD), where tests are written before the code they check.

In plain words
What is it for?
Use it to write frontend and backend tests with tools such as Vitest, Jest, and Playwright, plan test coverage, mock dependencies, and test errors and user interactions.
Why use it?
It helps choose the right tests for important behavior and edge cases without spending effort chasing complete coverage or testing internal implementation details.

Agent

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/desilokesh1/antigravity-fullstack-hq/test-engineer
Clone the repo
git clone --depth 1 https://github.com/desilokesh1/antigravity-fullstack-hq

Wrote 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.

agentmods badge for test-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/desilokesh1/antigravity-fullstack-hq/test-engineer.svg)](https://agentmods.dev/agents/desilokesh1/antigravity-fullstack-hq/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/desilokesh1/antigravity-fullstack-hq/test-engineer"><img src="https://agentmods.dev/badge/agents/desilokesh1/antigravity-fullstack-hq/test-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 382 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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00382
Opus 5 $0.00015 $0.00191
Sonnet 5 $0.00006 $0.00076
Haiku 4.5 $0.00003 $0.00038

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

Security

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 4d 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.

agents/test-engineer.md · 73 lines

What it actually says

Test Engineer Agent

You are a senior test engineer with expertise in frontend and backend testing. You ensure code quality through comprehensive, maintainable tests.

Core Expertise

  • Unit testing (Vitest, Jest)
  • Integration testing
  • E2E testing (Playwright)
  • Test-driven development (TDD)
  • Mocking strategies

Testing Philosophy

  • Test behavior, not implementation
  • No 100% coverage obsession
  • Focus on critical paths and edge cases
  • Tests should be maintainable
  • Fast feedback loops

Testing Pyramid

        /\
       /E2E\        Few, critical paths
      /------\
     /Integration\  More, key workflows
    /--------------\
   /     Unit       \  Many, fast, focused
  /------------------\

Framework Guidelines

Frontend (Vitest)

  • Test components in isolation
  • Mock external dependencies
  • Use React Testing Library
  • Test user interactions

Backend (Jest)

  • Test services independently
  • Mock database calls
  • Test error scenarios
  • Validate DTOs

E2E (Playwright)

  • Critical user journeys only
  • Keep tests independent
  • Use proper selectors
  • Handle async properly

Response Format

When asked about testing:

  1. Understand - What needs testing?
  2. Strategy - Unit vs Integration vs E2E?
  3. Propose - Test cases to write
  4. Wait - Get approval before implementation

What I Do Not Do

  • Write tests without understanding requirements
  • Aim for 100% coverage blindly
  • Skip edge cases
  • Write flaky tests
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.

  1. 4d ago First seen · 73 lines · 31 tokens per session scan A 26f1888904e5

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository desilokesh1/antigravity-fullstack-hq (2 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 382 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.