Borrowing it
Nothing to install: this file belongs to incubateur-ademe/benefriches. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/incubateur-ademe/benefriches/main/.claude/agents/e2e-coverage-checker.mdgit clone --depth 1 https://github.com/incubateur-ademe/benefrichesWrote 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/incubateur-ademe/benefriches/e2e-coverage-checker)<a href="https://agentmods.dev/agents/incubateur-ademe/benefriches/e2e-coverage-checker"><img src="https://agentmods.dev/badge/agents/incubateur-ademe/benefriches/e2e-coverage-checker/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/incubateur-ademe/benefriches/e2e-coverage-checker"><img src="https://agentmods.dev/badge/agents/incubateur-ademe/benefriches/e2e-coverage-checker.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.00039 | $0.01548 |
| Opus 5.5 | $0.00016 | $0.00619 |
| Sonnet 5.5 | $0.00008 | $0.00310 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
e2e-coverage-checker 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Coverage Checker
Analyze the current branch's changes against main and produce a structured report on whether e2e tests need to be created or updated.
Instructions
Step 1: Collect Diff
Run both commands and merge the results into a deduplicated list of changed files with their status (A=Added, M=Modified, D=Deleted):
git diff main...HEAD --name-status
git diff --name-status
If both commands return the same file, keep only one entry. Deleted files can be noted but don't need coverage analysis.
Step 2: Fast Pass — Classify by Path Pattern
For each changed file, check if it matches a trigger pattern:
| Pattern | Signal Type | Action |
|---|---|---|
apps/web/src/**/views/**/index.tsx |
New/modified container component | Trigger |
**/step-handlers/**/*.handler.ts |
New/modified wizard step | Trigger |
**/stepHandlerRegistry.ts |
Step registry change | Trigger |
apps/web/src/app/router.ts |
Route change | Trigger |
apps/api/src/**/*.controller.ts |
API endpoint change | Deep pass (Step 3) |
packages/shared/src/api-dtos/** |
Shared DTO change | Deep pass (Step 3) |
apps/e2e-tests/pages/** |
Page object change | Trigger (check for matching spec) |
| Everything else | — | Skip |
Files that don't match any pattern are excluded from the report entirely.
Step 3: Targeted Deep Pass
Only for files marked "Deep pass" in Step 2:
Shared DTOs (packages/shared/src/api-dtos/**):
- Extract the type name from the changed file (e.g.,
GetSiteViewResponseDtofromgetSiteView.dto.ts) - Grep
apps/e2e-tests/for that type name - If found: the change touches an already-covered flow — classify as "Covered" or "Partially covered"
- If not found: classify as "No coverage" but note this may be an internal DTO not directly used in e2e
API Controllers (apps/api/src/**/*.controller.ts):
- Read the controller to identify route paths (e.g.,
/api/sites,/api/reconversion-projects) - Grep
apps/e2e-tests/pages/andapps/e2e-tests/fixtures/helpers/for those route paths or the feature name - If found: classify as "Covered" or "Partially covered"
- If not found: classify as "No coverage"
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.
- 2mo ago First seen · 130 lines · 39 tokens per session scan A c8faa75faba7
e2e-coverage-checker is an agent published in the GitHub repository incubateur-ademe/benefriches (45 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,548 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-08-30.
Other agents, from other repositories
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…
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-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
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.
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.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.