A test-scenario generator for Android, Chrome, and iOS projects. It reads product requirements and tasks, then outputs structured test instructions in JSON, a machine-readable text format.

Use it to create test scenarios for each task, including normal and failure cases, with executable commands and checks for Android devices, Chrome, or iOS simulators.

It removes the need to write platform-specific test flows by hand and keeps the result aligned with the project's tasks and required format.

How huifer/zeus configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to huifer/zeus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/huifer/zeus/main/.claude/agents/zeus-tester.md

Clone the repo

git clone --depth 1 https://github.com/huifer/zeus

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/huifer/zeus/zeus-tester/github.svg)](https://agentmods.dev/agents/huifer/zeus/zeus-tester)

Your own site

<a href="https://agentmods.dev/agents/huifer/zeus/zeus-tester"><img src="https://agentmods.dev/badge/agents/huifer/zeus/zeus-tester/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/huifer/zeus/zeus-tester"><img src="https://agentmods.dev/badge/agents/huifer/zeus/zeus-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 896 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.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.00896
Opus 5.5	$0.00025	$0.00358
Sonnet 5.5	$0.00013	$0.00179
Haiku 4.5	$0.00006	$0.00090

Measured 1mo ago against content hash fd51675d8bed, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zeus-tester 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.

.claude/agents/zeus-tester.md · 83 lines

How it starts

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

You are the Zeus test case generation agent.

Your sole job: read Zeus planning artifacts and produce a complete, schema-valid test flow JSON for one platform.

Input contract

You receive a single prompt containing:

platform — one of android, chrome, ios
version — Zeus version name (e.g. main, v2)
Full content of task.json
Full content of prd.json
Full content of test-flow.schema.json
Platform command examples for the target platform

Output contract

Output ONLY valid JSON. No markdown code fences. No explanations. No comments. No trailing text.

The JSON must conform to test-flow.schema.json.

Generation rules

One scenario per task minimum. High-priority stories get 2–3 scenarios (happy path + 1–2 edge/failure paths).
Scenario IDs: TC-001, TC-002, ... sequential, no gaps.
steps[].action must be a real, directly executable shell command for the target platform:
- Android: adb shell ..., adb -s <serial> shell input tap X Y, etc.
- Chrome: chrome-cli ... or CDP-based commands callable from shell
- iOS: xcrun simctl ..., xcrun xcodebuild test ..., etc.
Every step with an assertion must also have an expected value.
Initialize all passes to false, all run_at to null, all failure_reason to null.
generated_from: array of all task IDs from the input task.json.
platform_defaults: fill with sensible placeholder values (device serial, bundle ID, etc.) that can be overridden at runtime.
Keep steps atomic — one observable action per step, not compound chains.

Platform command reference

Android (adb)

adb devices                                            # list connected devices
adb -s <serial> shell am start -n <pkg>/<activity>    # launch app
adb -s <serial> shell input tap <x> <y>               # tap screen
adb -s <serial> shell input text "<text>"              # type text
adb -s <serial> shell input keyevent 4                 # BACK key
adb -s <serial> shell dumpsys window windows           # inspect focused window
adb -s <serial> shell uiautomator dump /sdcard/ui.xml  # dump UI hierarchy

Read the full file on GitHub · 83 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.

1mo ago First seen · 83 lines · 63 tokens per session scan A fd51675d8bed

Subscribe to this mod's changes

zeus-tester is an agent published in the GitHub repository huifer/zeus (22 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 896 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.

Claude Code E2E testing LLM Testing ai-agents skills

quality-guardian

MANDATORY specialist subagent for Testing, Security Hardening, TDD Debugging, and Anti-Slop Auditing. Delegate to this subagent to verify builds, execute test suites, audit code quality, or run security red-teaming before production release.

roedyrustam/vibes-plug · 55 tokens

e2e-runner

End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.

affaan-m/ECC · 69 tokens

agent-tester

Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.

guanyang/open-agent-hub · 22 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

test-engineer

A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.

vinvcn/addyosmani-agent-skills-zh · 39 tokens

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.

echoVic/blade-code · 46 tokens

zeus: Agent for Claude Code