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/skills/run-e2e-tests/SKILL.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/skills/incubateur-ademe/benefriches/run-e2e-tests)<a href="https://agentmods.dev/skills/incubateur-ademe/benefriches/run-e2e-tests"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/run-e2e-tests/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/skills/incubateur-ademe/benefriches/run-e2e-tests"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/run-e2e-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00097 | $0.00448 |
| Opus 5 | $0.00048 | $0.00224 |
| Sonnet 5 | $0.00019 | $0.00090 |
| Haiku 4.5 | $0.00010 | $0.00045 |
Grade A, and why
run-e2e-tests 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 12d 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
Run E2E Tests
Run the full e2e test lifecycle: start stack, run tests, stop stack.
Arguments
$ARGUMENTS(optional): Test path filter passed toplaywright test(e.g.,tests/create-site/,tests/create-project/create-photovoltaic-project.spec.ts)
Procedure
Execute these steps sequentially. Stop and report on failure at any step.
1. Build Docker images, start the stack, and wait for readiness
cd $PROJECT_ROOT
make e2e-up-build
This builds quietly and blocks until every service (including web) reports healthy via its Docker healthcheck. If it fails or times out, run docker compose --env-file .env.e2e -f docker-compose.e2e.yml logs --tail=50 to show recent logs, then stop.
2. Run the tests
If $ARGUMENTS is provided:
pnpm --filter e2e-tests test:headless $ARGUMENTS
Otherwise:
pnpm --filter e2e-tests test:headless
3. Tear down the stack
Only if tests passed:
docker compose --env-file .env.e2e -f docker-compose.e2e.yml down
If tests failed, keep the stack running and inform the user so they can investigate. Mention they can manually stop it with docker compose --env-file .env.e2e -f docker-compose.e2e.yml down.
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.
- 12d ago First seen · 53 lines · 97 tokens per session scan A c7e0e87c80ec
run-e2e-tests is a skill published in the GitHub repository incubateur-ademe/benefriches (45 stars, last pushed 3d ago), licensed MIT. It adds 97 tokens to every session and 448 once invoked, about $0.0005 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-30.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…