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/desilokesh1/antigravity-fullstack-hqWrote 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/desilokesh1/antigravity-fullstack-hq/test-engineer)<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/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/desilokesh1/antigravity-fullstack-hq/test-engineer"><img src="https://agentmods.dev/badge/agents/desilokesh1/antigravity-fullstack-hq/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.00031 | $0.00382 |
| Opus 5.5 | $0.00012 | $0.00153 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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.
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:
- Understand - What needs testing?
- Strategy - Unit vs Integration vs E2E?
- Propose - Test cases to write
- 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
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 · 73 lines · 31 tokens per session scan A 26f1888904e5
test-engineer is an agent published in the GitHub repository desilokesh1/antigravity-fullstack-hq (2 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 382 once invoked, about $0.0001 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-31.
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.