A command that creates a test suite for a selected file or component and prioritizes tests using code complexity and business importance.

Use it to generate unit, integration, end-to-end, snapshot, and accessibility tests as appropriate, then run them and report the results.

It helps focus testing effort on important or complicated code while still checking edge cases and error paths.

test — Command for coding agents by senaiverse: A command that creates a test suite for a…

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 commands/senaiverse/reactnative-expo-ai-agent-system-workflow/test

Clone the repo

git clone --depth 1 https://github.com/senaiverse/reactnative-expo-ai-agent-system-workflow

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/test.svg)](https://agentmods.dev/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/test)

Your own site

<a href="https://agentmods.dev/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/test"><img src="https://agentmods.dev/badge/commands/senaiverse/reactnative-expo-ai-agent-system-workflow/test.svg" alt="Measured on agentmods" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 408 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00408
Opus 5	$0.00006	$0.00204
Sonnet 5	$0.00002	$0.00082
Haiku 4.5	$0.00001	$0.00041

Measured 5d ago against content hash 16eb8ff52ddb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

test scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

ready-to-use/commands/test.md · 89 lines

What it actually says

Generate Test Suite

Generating tests for: $ARGUMENTS

Test Generation Workflow

Step 1: Analyze Target

Read the file/component
Assess complexity (lines, cyclomatic complexity, dependencies)
Determine business criticality
Calculate test priority: Complexity × Criticality

Step 2: Determine Test Strategy (@test-architect)

CRITICAL Priority:

E2E tests (full user journey)
Integration tests (API, state)
Unit tests (logic)
Edge case coverage

HIGH Priority:

Integration tests
Unit tests
Basic edge cases

MEDIUM Priority:

Unit tests
Snapshot tests

LOW Priority:

Snapshot tests only (or skip)

Step 3: Generate Tests (@test-generator)

Create test files with:

Proper setup/teardown
Mocking (API, navigation, etc.)
Async handling
Edge cases
Accessibility checks
Clear test descriptions

Step 4: Run Tests

npm test -- [test-file]

Report:

✅ Tests passing
❌ Tests failing (with fixes)
Coverage percentage

Step 5: Validation

Ensure:

Tests are meaningful (not just coverage boosting)
Edge cases covered
Error paths tested
Async operations handled correctly

Output

Tests Generated: X Coverage: Before X% → After Y% Test Types:

Unit: X tests
Integration: X tests
E2E: X tests

Files Created:

[List test files]

To Run:

npm test

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.

5d ago First seen · 89 lines · 12 tokens per session scan C 16eb8ff52ddb

Subscribe to this mod's changes

test is a command published in the GitHub repository senaiverse/reactnative-expo-ai-agent-system-workflow (125 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 408 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Testing Unit testing ai-agents claude-agents claude-code code-quality developer-tools expo

golang-test-review

Use when reviewing Go test code (new or changed test.go files, test harnesses, fixtures, or test tooling) for a Go-test-expert pass — behavior-over-surface, determinism, parallel-safety, build-tag correctness, and harness reuse. Complements the general code-reviewer with test-specific rigor.

mickeyyaya/evolve-loop · 65 tokens

test