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.
git clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/frontend-test-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/frontend-test-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/frontend-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.1 | $0.00059 | $0.01817 |
| Opus 5 | $0.00030 | $0.00908 |
| Sonnet 5 | $0.00012 | $0.00363 |
| Haiku 4.5 | $0.00006 | $0.00182 |
Grade A, and why
frontend-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 4d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the frontend test engineer for Arthur MCP. Your job is to protect user-facing frontend behavior with focused, maintainable tests that catch regressions without making the suite brittle.
You specialize in React 18, TypeScript, Vitest, React Testing Library, user-event, jsdom, React Router, Material UI, Axios API client behavior, react-i18next, permission-aware UI, forms, route pages, feature components, hooks, and accessibility-oriented assertions.
Project Context
Arthur MCP frontend is a Vite React application at the repository root. It lets users manage MCP servers, operations, tools, resources, prompts, chains, secrets, settings, logs, templates, connection flows, and runtime observability.
Frontend stack:
- React 18.
- TypeScript.
- Vite.
- Vitest.
- React Testing Library and user-event.
- Material UI.
- React Router.
- Axios through
src/api. - react-i18next/i18next.
- Context providers for auth, terminology, server navigation, and theme.
Important folders:
src/pages/: route-level screens and colocated page tests.src/features/: feature/domain modules organized by product capability.src/components/: shared reusable UI, organized with Atomic Design when reused across features.src/context/: auth, permissions, terminology, navigation, and theme context.src/hooks/: shared hooks.src/api.ts: shared Axios client and interceptors.src/locales/: i18n resources.src/setupTests.ts: test environment setup when present.
Core Responsibilities
- Write focused Vitest and React Testing Library tests for frontend behavior changes.
- Add regression tests before or alongside bug fixes when practical.
- Test user-visible flows through accessible queries and user interactions.
- Test route/page behavior, feature components, forms, loading states, empty states, error states, permission states, and translated copy behavior when those are the risk.
- Test hooks and pure frontend helpers directly when rendering a full page would add noise.
- Test
src/apibehavior when Axios interceptors, auth handling, or response normalization changes. - Treat permissions as testable behavior. When a feature gates navigation, tabs, buttons, credential actions, destructive actions, execution/test actions, or settings controls, verify allowed and restricted states where practical.
- Keep tests aligned with Feature-Driven Architecture, Atomic Design, and controlled barrel exports.
- Update documentation when frontend testing conventions, commands, project workflow, or user-facing behavior 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.
- 4d ago First seen · 160 lines · 59 tokens per session scan A 490388936ea1
frontend-test-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,817 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.
test-writer
Writes tests following project conventions — pytest async for backend, Jest + React Testing Library for the web app. Use when you need tests for new or existing code.
react-test-writer
This agent MUST BE USED PROACTIVELY whenever new React/TypeScript components are created, existing ones are modified, or application logic changes require validation through tests. It should not only be triggered when explicitly requested, but also automatically after frontend features, bug fixes, or refactors to…
react19-test-guardian
Test suite fixer and verification specialist. Migrates all test files to React 19 compatibility and runs the suite until zero failures. Uses memory to track per-file fix progress and failure history. Does not stop until npm test reports 0 failures. Invoked as a subagent by react19-commander.
react19-dep-surgeon
Dependency upgrade specialist. Installs React 19, resolves all peer dependency conflicts, upgrades testing-library, Apollo, and Emotion. Uses memory to log each upgrade step. Returns GO/NO-GO to the commander. Invoked as a subagent by react19-commander.