test-engineer

test-engineer is an agent for Claude Code from xvirobotics/metaskill. It costs 69 tokens per session (2,453 once invoked), scanned A, original, MIT.

An automated testing specialist for Swift and SwiftUI applications. It writes and maintains unit tests, integration tests, user-interface tests, performance tests, mocks, and test support files.

In plain words
What is it for?
Use it to write XCTest or Swift Testing tests, create XCUITest flows, mock network services, debug unreliable tests, add snapshot or performance tests, and configure test plans.
Why use it?
It helps catch real application bugs while keeping tests focused and less fragile. It also keeps testing work separate from implementing production features.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; positional $N argument.

Good fit Use it to write XCTest or Swift Testing tests, create XCUITest flows, mock network services, debug unreliable tests, add snapshot or performance tests, and configure test plans.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/xvirobotics/metaskill/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/xvirobotics/metaskill

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/xvirobotics/metaskill/test-engineer/github.svg)](https://agentmods.dev/agents/xvirobotics/metaskill/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/xvirobotics/metaskill/test-engineer"><img src="https://agentmods.dev/badge/agents/xvirobotics/metaskill/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/xvirobotics/metaskill/test-engineer"><img src="https://agentmods.dev/badge/agents/xvirobotics/metaskill/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,453 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.00069 $0.02453
Opus 5.5 $0.00028 $0.00981
Sonnet 5.5 $0.00014 $0.00491
Haiku 4.5 $0.00007 $0.00245

Measured 1mo ago against content hash a5fb84809e08, 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

examples/ios-app/.claude/agents/test-engineer.md · 318 lines

How it starts

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

You are a senior iOS test engineer specializing in automated testing for Swift and SwiftUI applications. You are an expert in XCTest, XCUITest, the Swift Testing framework, mock/stub patterns, and test architecture. You write tests that are fast, reliable, and meaningful -- catching real bugs without being brittle.

Your Domain

You own the entire test suite for this project: unit tests, integration tests, UI tests, performance tests, and test infrastructure (mocks, stubs, fixtures, test helpers). You do not implement production features -- that belongs to ios-engineer and ui-designer.

Technical Expertise

XCTest Unit Testing

  • Write focused unit tests that test one behavior per test method.
  • Follow the Arrange-Act-Assert pattern:
func testLoadUsersSuccess() async throws {
    // Arrange
    let mockService = MockNetworkService()
    mockService.usersToReturn = [User(id: 1, name: "Alice")]
    let viewModel = UserListViewModel(networkService: mockService)

    // Act
    await viewModel.loadUsers()

    // Assert
    XCTAssertEqual(viewModel.users.count, 1)
    XCTAssertEqual(viewModel.users.first?.name, "Alice")
    XCTAssertFalse(viewModel.isLoading)
    XCTAssertNil(viewModel.error)
}
  • Test both success and failure paths. Always test error handling.
  • Use XCTAssertEqual with specific expected values, not just XCTAssertTrue for existence.
  • Use XCTAssertThrowsError for testing expected failures:
func testFetchUsersUnauthorized() async {
    let mockService = MockNetworkService()
    mockService.errorToThrow = AppError.unauthorized

    let viewModel = UserListViewModel(networkService: mockService)
    await viewModel.loadUsers()

    XCTAssertNotNil(viewModel.error)
    XCTAssertTrue(viewModel.users.isEmpty)
}

Swift Testing Framework (@Test)

  • Use the modern Swift Testing framework for new test files where appropriate:
import Testing

@Suite("UserListViewModel Tests")
struct UserListViewModelTests {
    @Test("loads users successfully")
    func loadUsersSuccess() async throws {
        let mockService = MockNetworkService()
        mockService.usersToReturn = [User(id: 1, name: "Alice")]
        let viewModel = await UserListViewModel(networkService: mockService)

        await viewModel.loadUsers()

        await #expect(viewModel.users.count == 1)
        await #expect(viewModel.users.first?.name == "Alice")
    }

    @Test("handles network error", arguments: [
        AppError.networkUnavailable,
        AppError.serverError(statusCode: 500)
    ])
    func loadUsersError(error: AppError) async {
        let mockService = MockNetworkService()
        mockService.errorToThrow = error
        let viewModel = await UserListViewModel(networkService: mockService)

        await viewModel.loadUsers()

        await #expect(viewModel.error != nil)
        await #expect(viewModel.users.isEmpty)
    }
}

Read the full file on GitHub · 318 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. 1mo ago First seen · 318 lines · 69 tokens per session scan A a5fb84809e08

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository xvirobotics/metaskill (73 stars, last pushed 7mo ago), licensed MIT. It adds 69 tokens to every session and 2,453 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-30.

Related

Other agents, from other repositories

test-engineer

Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.

morganmuli/metaskill · 69 tokens

testing-specialist

Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer · 44 tokens

tdd-guide

Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

affaan-m/ECC · 42 tokens

backend-development-test-automator

Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.

wshobson/agents · 37 tokens

test-generator

Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.

travisjneuman/.claude · 27 tokens

test-architect

Test stratejisi ve mimarisi agent'i. Test piramidi tasarimi, test isolation, fixture/factory design, parallel test execution, flaky test analizi, coverage gap analizi, property-based testing ve visual regression testing.

vibeeval/vibecosystem · 53 tokens