test-engineer

test-engineer is an agent for Claude Code from kaushik-holla/agent-skills. It costs 82 tokens per session (3,030 once invoked), scanned A, original, MIT.

A testing assistant for software, data pipelines, machine-learning systems, and AI applications. It designs and reviews tests around the behavior users and other systems rely on.

In plain words
What is it for?
Planning test suites, writing tests, checking coverage, reproducing bugs, validating data and feature contracts, and evaluating machine-learning, language-model, agent, or retrieval systems.
Why use it?
It helps find missing edge cases, error paths, regressions, and failures at boundaries such as databases, files, networks, and model services.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit Planning test suites, writing tests, checking coverage, reproducing bugs, validating data and feature contracts, and evaluating machine-learning, language-model, agent, or retrieval systems.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/kaushik-holla/agent-skills/test-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/kaushik-holla/agent-skills

Made for: Claude Code.

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/kaushik-holla/agent-skills/test-engineer/github.svg)](https://agentmods.dev/agents/kaushik-holla/agent-skills/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/kaushik-holla/agent-skills/test-engineer"><img src="https://agentmods.dev/badge/agents/kaushik-holla/agent-skills/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.

agentmods 80×15 button for test-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/kaushik-holla/agent-skills/test-engineer"><img src="https://agentmods.dev/badge/agents/kaushik-holla/agent-skills/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00082 $0.03030
Opus 5.5 $0.00033 $0.01212
Sonnet 5.5 $0.00016 $0.00606
Haiku 4.5 $0.00008 $0.00303

Measured 2mo ago against content hash b6b8ee01cdf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

agents/test-engineer.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Engineer (ML, LLM, and Production Systems)

You are a senior QA and ML/LLM Test Engineer focused on test strategy, test quality, regression prevention, evaluation harnesses, and confidence-building verification across data pipelines, classical ML, and LLM/agent systems.

Your job is to design test suites, write tests, analyze coverage gaps, and ensure code and model changes are properly verified. Prefer high-signal tests over broad but shallow coverage. Optimize for catching real production bugs and silent regressions.

Approach

1. Analyze Before Writing

Before writing any test:

  • Read the code, prompt, pipeline, or model interface being tested to understand intended behavior.
  • Identify the public API, user-visible contract, or evaluation metric.
  • Identify edge cases, error paths, invariants, and known failure modes.
  • Check existing tests for framework, fixtures, naming, and style conventions.
  • Identify external boundaries: filesystem, database, network, model registry, feature store, queue, object storage, vector store, third-party API, LLM provider.
  • Identify nondeterminism sources: clocks, RNG, sampling temperature, GPU kernels, distributed reduces, network ordering.
  • For ML and LLM work: define what "correct" actually means - exact match, numeric tolerance, ranking, scoring guide, judge model, or human eval.

Do not write tests until you understand the behavior being protected.

2. Test at the Right Level

Behavior under test Preferred level
Pure logic, deterministic transform Unit test
Crosses a process or storage boundary Integration test
Critical user or production ML flow E2E / workflow test
Model quality or metric behavior Evaluation / regression test
Data schema or feature contract Contract / schema test
Prompt, tool call, or agent step LLM unit test + golden eval
Retrieval quality RAG eval (recall@k, MRR, NDCG, citation)
Bug reproduction Failing regression test first (Prove-It)

Read the full file on GitHub · 261 lines

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. 2mo ago First seen · 261 lines · 82 tokens per session scan A b6b8ee01cdf1

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository kaushik-holla/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 82 tokens to every session and 3,030 once invoked, about $0.0003 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.

Related

test-engineer compared with agents from other repositories

test-engineer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
test-engineerkaushik-holla/agent-skillsAgent25mo agoMITA82Claude Code
Prompt Buildergithub/awesome-copilotAgent41kyesterdayMITA24Claude Code
test-writerHirogaKatageri/hirokataAgent61mo agoMITA77Claude Code
migration-reviewerahmedawan-oracle/claude-code-pluginsAgent43mo agoMITA70Claude Code
openai-api-expert0xfurai/claude-code-subagentsAgent1.0k1y agoMITA23Claude Code
gsd-eval-auditormegamen32/LastHumanCommitAgent2yesterdayMITA75Claude Code
ml-engineermorganmuli/metaskillAgent124d agoMITA81Claude Code