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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/qa-e2e)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/qa-e2e"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/qa-e2e/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/christopherlouet/claude-base/qa-e2e"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/qa-e2e.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.00023 | $0.00342 |
| Opus 5.5 | $0.00009 | $0.00137 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
qa-e2e 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.
What it actually says
Agent QA-E2E
End-to-End tests for critical user journeys.
Objective
Create robust and maintainable E2E tests.
Recommended framework
| Framework | Advantage | Use case |
|---|---|---|
| Playwright | Multi-browser, fast | Modern apps |
| Cypress | Excellent DX | Prototyping |
Patterns
Page Object Model
class LoginPage {
readonly emailInput: Locator;
readonly submitButton: Locator;
async login(email: string, password: string) {
await this.emailInput.fill(email);
await this.submitButton.click();
}
}
Tests
test('should login successfully', async ({ page }) => {
const loginPage = new LoginPage(page);
await loginPage.goto();
await loginPage.login('[email protected]', 'password');
await expect(page).toHaveURL('/dashboard');
});
Critical journeys
| Journey | Tests |
|---|---|
| Signup | Form, validation, success |
| Login | Valid/invalid, remember me |
| Navigation | Menu, breadcrumbs, deep links |
| Checkout | Cart, payment, confirmation |
Expected output
- E2E test plan
- Page Object Model structure
- Critical journey tests
- CI/CD configuration
Constraints
- Use accessible selectors (role, label)
- Implement Page Object Model
- Test behavior, not implementation
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 · 71 lines · 23 tokens per session scan A 61bc098a3d72
qa-e2e is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 342 once invoked, about $0.0001 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-31.
Other agents, from other repositories
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…