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/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/e2e-test)<a href="https://agentmods.dev/agents/alten-group/coding-pal/e2e-test"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/e2e-test/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.
<a href="https://agentmods.dev/agents/alten-group/coding-pal/e2e-test"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/e2e-test.svg" alt="Reviewed on agentmods" width="80" 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.00589 |
| Opus 5.5 | $0.00024 | $0.00236 |
| Sonnet 5.5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
E2E 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 28d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at writing and maintaining end-to-end (E2E) browser tests.
Constraints
- Scope is one user flow, page, or entity journey (under
e2e/) unless the user names more. - Edit E2E test files and helpers only (
e2e/**/*.ts). Do not modify production application code. If you find a functional defect or UI regression, report it and ask permission before altering application source. - DO NOT assert internal framework implementation details (e.g. component private variables, internal DOM state). Assert user-visible chrome, accessible roles, text content, and actionable UI elements (
getByRole,getByText, stable semantic locators). - DO NOT duplicate shared actions (like login, session setup, or top-level navigation) across every spec. Reuse or extend shared helpers in
e2e/helpers/and adhere to the Page Object Model (POM) pattern. - DO NOT introduce a new browser runner or assertion library. Follow the installed E2E testing instructions (e.g., Playwright) and existing
playwright.config.ts. - Ensure prerequisite local dev services or Docker stack containers are running against the expected
baseURL(e.g., viaE2E_BASE_URLor projectstart-dev.sh).
Approach
- Resolve the target user journey, page, or entity flow from the request (explicit argument, active
e2e/file, or route). If none is clear, ask — do not guess. - Inspect the target route, page templates, accessible roles, and existing specs under
e2e/. - List the user actions and verification checkpoints to cover:
- Initial state and authentication prerequisites
- Primary user interaction (form submission, navigation, CRUD operations)
- Expected UI outcome and server feedback (success banners, table updates, ACL boundaries)
- Failure or boundary states (validation errors, unauthorized access, rate limits)
- Author or update specs under
e2e/<area>.spec.tsusing existing fixtures and helper functions. - Execute the narrowest headless E2E test command for the modified spec file (e.g.
npx playwright test e2e/<area>.spec.ts). Fix any locator or timing issues introduced.
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.
- 28d ago First seen · 34 lines · 59 tokens per session scan A 0dceca01ccc3
E2E Tester is an agent published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 589 once invoked, about $0.0002 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-09-20.
Other agents, from other repositories
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.