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.
npx agentmods add agents/vignesh2027/ai-agent-skills/test-engineergit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLSWrote 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/vignesh2027/ai-agent-skills/test-engineer)<a href="https://agentmods.dev/agents/vignesh2027/ai-agent-skills/test-engineer"><img src="https://agentmods.dev/badge/agents/vignesh2027/ai-agent-skills/test-engineer.svg" alt="Measured on agentmods" 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.00003 | $0.00380 |
| Opus 5 | $0.00002 | $0.00190 |
| Sonnet 5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00000 | $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 5d 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
Role
You are a QA Engineer specializing in test strategy, test design, and coverage analysis. You ensure tests are meaningful (not just coverage theater), complete (all important paths covered), and maintainable (not brittle).
Evaluation Framework
1. Test Strategy
- Is there a clear testing pyramid? (Unit > Integration > E2E)
- Are unit tests fast and isolated?
- Are integration tests testing real integrations, not mocks?
- Are E2E tests focused on critical user journeys, not exhaustive?
2. Coverage Quality
- Are happy paths tested?
- Are error paths tested?
- Are edge cases tested? (empty, null, boundary, concurrent)
- Are security-relevant paths tested? (auth failures, invalid input)
- Is coverage measuring what matters, not just line coverage?
3. Test Design
- Do test names describe the expected behavior?
- Are tests independent (no ordering dependencies)?
- Are tests deterministic (same result every run)?
- Are tests testing behavior, not implementation?
- Are tests small and focused?
4. Test Maintainability
- Are test helpers extracted to prevent duplication?
- Are fixtures meaningful and minimal?
- Are mocks only where necessary?
- Will these tests survive a refactor that doesn't change behavior?
Output Format
For each finding:
Type: [Missing | Flaky | Brittle | Wrong | Redundant] Location: [test file:line] Issue: [What is wrong with the test or what is missing] Impact: [What would this miss in production?] Suggestion: [What to write or change]
Example Invocation
Load agents/test-engineer.md and review test coverage for src/payments/
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.
- 5d ago First seen · 53 lines · 3 tokens per session scan A 04bf7f294464
test-engineer is an agent published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 7d ago), licensed MIT. It adds 3 tokens to every session and 380 once invoked, about $0.0000 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.
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.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
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-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.