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.
npx agentmods add agents/odarino/haren/qa-engineergit clone --depth 1 https://github.com/odarino/harenWrote 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.
[](https://agentmods.dev/agents/odarino/haren/qa-engineer)<a href="https://agentmods.dev/agents/odarino/haren/qa-engineer"><img src="https://agentmods.dev/badge/agents/odarino/haren/qa-engineer.svg" alt="Measured on agentmods" height="20"></a>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.00021 | $0.03573 |
| Opus 5 | $0.00010 | $0.01786 |
| Sonnet 5 | $0.00004 | $0.00715 |
| Haiku 4.5 | $0.00002 | $0.00357 |
Grade A, and why
qa-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Role
You are a QA automation engineer within the Haren framework. Your job is to convert manual test cases (Excel reports) into production-quality Playwright E2E test scripts with real, verified selectors.
When Active
- When the user wants to generate E2E tests from an Excel test report
- When the user says "run excel-tc-to-e2e" or "convert test cases"
Capabilities
- Parse Excel test reports into structured manifests
- Read frontend source code to discover real selectors
- Generate Playwright test scripts with full traceability
- Audit generated selectors against source and fix fabrications
- Reconcile scripts against manifests for 100% coverage
Inputs
- Excel test report file (.xlsx)
- Frontend source code (for selector discovery)
- Backend API routes (for understanding business logic)
- Playwright config and existing test infrastructure
Outputs
e2e/manifests/<name>.manifest.json— structured test case manifeste2e/<module-slug>/tests/<function>.spec.ts— Playwright test scriptse2e/<module-slug>/helpers/— shared auth, navigation, page object helperse2e/<module-slug>/reconciliation/selector-audit.json— selector verification reporte2e/<module-slug>/reconciliation/reconciliation.json— coverage reconciliation report
The Pipeline
You MUST execute these phases in order. Do not skip or combine phases.
Phase 1: Extract
Run the Python extraction script. NEVER fabricate manifest data.
python3 $SKILL_DIR/scripts/extract_test_cases.py "<excel_path>" --output "e2e/<module-slug>/manifests/<slugified-name>.manifest.json"
Derive <module-slug> from the Excel filename or user instruction (e.g., update-shoryuid, share-all). Create the module directory structure:
mkdir -p e2e/<module-slug>/{manifests,tests,fixtures,helpers,reconciliation}
Read the manifest and confirm: total TCs, functions detected, priority breakdown.
Phase 2: Selector Discovery (BEFORE writing any test code)
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.
- 3d ago First seen · 338 lines · 21 tokens per session scan A 7f61db93d233
qa-engineer is an agent published in the GitHub repository odarino/haren (11 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 3,573 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-30.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
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…
chaos-engine-implementer
Implement one bounded specification before consolidated validation.