test-engineer

A testing guide for TypeScript, React, and Rust code, using Vitest for JavaScript tests and Cargo's built-in test tools for Rust. It focuses on tests that catch real implementation failures.

In plain words
What is it for?
Use it when creating tests for React components, state stores, schemas, backend commands, or Rust modules, after identifying their public functions and important scenarios.
Why use it?
It helps replace shallow or placeholder tests with checks for normal behaviour, edge cases, errors, dependencies, and side effects.

Skill for Claude CodeCodex

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 skills/recusive/skills/test-engineer
Any agent
npx skills add Recusive/Skills --skill test-engineer
Clone the repo
git clone --depth 1 https://github.com/Recusive/Skills

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,097 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.00024 $0.02097
Opus 5 $0.00012 $0.01048
Sonnet 5 $0.00005 $0.00419
Haiku 4.5 $0.00002 $0.00210

Measured 2d ago against content hash 191b91075793, 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 2d 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.

test-engineer/SKILL.md · 295 lines

How it starts

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

Test Engineer Skill

Write tests that fail when implementation breaks. No placeholders, no expect(true).toBe(true).

Process

Step 1: Read the File

Use Read tool to read the entire file. Identify:

  • Type: React component, Zustand store, Zod schema, Rust module, Tauri command
  • Public API: Exported functions, actions, props, methods
  • Dependencies: Imports, external calls (Tauri invoke, APIs)
  • Middleware: persist, immer, devtools (for Zustand stores)
  • Side effects: API calls, state mutations, filesystem operations

Step 2: Output Analysis (MANDATORY)

Before writing ANY test code, output:

## Analysis: [filename]

**Type:** [React Component | Zustand Store | Zod Schema | Rust Module | Tauri Command]
**Purpose:** [1-2 sentences]
**Middleware:** [persist | immer | none] (if Zustand)

**Public API:**
- `functionName`: [what it does]

**Test Scenarios:**
1. [Happy path]
2. [Edge case]
3. [Error case]

**Skip Testing:**
- [Any pass-through functions or trivial code]

Step 3: Write Tests

See references/templates.md for framework-specific templates.

Framework Selection

File Type Framework Mock Strategy
Zustand Store (/stores/*.ts) Vitest Mock @tauri-apps/api/core if store calls invoke
Zustand + persist Vitest Test partialize and merge callbacks
React Component (*.tsx) Vitest + RTL Custom render with providers
Zod Schema (/schemas/*.ts) Vitest None needed
Rust Module (*.rs) cargo test tempfile for filesystem
Tauri Command (/commands/*.rs) #[tokio::test] tempfile, real backend

Read the full file on GitHub · 295 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 295 lines · 24 tokens per session scan A 191b91075793

Subscribe to this mod's changes

test-engineer is a skill published in the GitHub repository Recusive/Skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 2,097 once invoked, about $0.0001 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.