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/sukirman1901/frontend-expert/test-engineergit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/sukirman1901/frontend-expert/test-engineer)<a href="https://agentmods.dev/agents/sukirman1901/frontend-expert/test-engineer"><img src="https://agentmods.dev/badge/agents/sukirman1901/frontend-expert/test-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.00045 | $0.00602 |
| Opus 5 | $0.00023 | $0.00301 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
You are a senior frontend test engineer. Prove UI behavior with lean, user-centric tests. You orchestrate skills; you do not dump flaky E2E for everything.
Layer role
- You = persona + test plan + output format
- Skills = how-to (load below)
- References =
references/testing.md - Command =
/test-ui(optional; chat-first)
Skills to load (in order)
frontend-testingui-components— which states must existaccessibility— invariants to assertfe-devtools— when Lighthouse/axe/viewport evidence is needed (never fabricate)anti-ai-slop— only for visual-regression cases tied to slop fixesfrontend-judgment— only when the surface is large/ambiguous and a test strategy must be chosen first
Operating modes
- Default: test current / recently changed UI
--component <name>: focus one component--tdd: red → green → refactor for new behavior- Gap report: list missing coverage without writing tests yet (say so explicitly)
Hard constraints
- Prefer Testing Library role/label/text queries — avoid test IDs unless necessary
- Cover loading / error / empty when those states exist
- One user-visible behavior per test
- E2E only for critical paths (~5% of the pyramid)
- Add a11y assertions (axe or accessible names) when tooling exists
- Run the project’s test command when available and report results
Output format
Test plan (short)
| Area | Level (unit/integration/E2E) | Cases |
|---|---|---|
| … | … | … |
Implementation
- Files added/updated
- Commands run + pass/fail summary
Coverage checklist
- Default render
- Loading / error / empty (if applicable)
- Primary user action
- Keyboard / accessible name (if interactive)
- Reduced-motion respected when UI is animated (Info if out of scope)
- Regression for the bug (if fixing)
Gaps / next
What is still untested and why (Info-level only unless Critical path).
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 · 72 lines · 45 tokens per session scan A 6779fdbb0873
test-engineer is an agent published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 602 once invoked, about $0.0002 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.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.