Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dayvisonassis/sdd-skillsnpx agentmods add skills/dayvisonassis/sdd-skills/e2e-test-writerWrote 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/dayvisonassis/sdd-skills/e2e-test-writer)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/e2e-test-writer"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/e2e-test-writer/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/dayvisonassis/sdd-skills/e2e-test-writer"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/e2e-test-writer.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.00195 | $0.03598 |
| Opus 5.5 | $0.00078 | $0.01439 |
| Sonnet 5.5 | $0.00039 | $0.00720 |
| Haiku 4.5 | $0.00019 | $0.00360 |
Grade A, and why
e2e-test-writer 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 18d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Writer
Plan and implement end-to-end tests that drive the running app through a real browser: a user acts on the screen and the test asserts what observably follows. Never modifies production code, the e2e harness, or the visual suite — if a test fails, only the test is adjusted, and only when the test is what is wrong.
The project defines the harness; this skill defines the discipline. All hard rules (project profile, boundary, harness, structure, session, assertions, data, coverage outcomes, execution) are in
references/e2e-rules.md— read it before writing. Its first section tells you what to read from the project'sGATES.md: profiles, folders, test language, fixtures, API origin, build log, gate and data policy. Mechanics for exploring a live flow and turning actions into code come from theplaywright-cliskill:../playwright-cli/references/spec-driven-testing.mdand../playwright-cli/references/test-generation.md. Where they conflict withe2e-rules.md(one test per file,specs/*.plan.md, a seed that logs in),e2e-rules.mdwins. Generic SDD flow docs:https://github.com/dayvisonassis/sdd-skills/blob/main/docs/GUIA_DO_WORKFLOW.md.
Scope: the e2e test directory the project profile names — one folder per profile.
INPUT
feature(required when a contract exists) — the feature folder's id (F14,F08-v2); locatesdocs/<feature-id>-<kebab>/contract.md.target(required) — what to cover: contract surface ids (UI-02), criterion ids (OC-08), or a route for work outside a contract (then the route's slug stands in for the surface id in the file name and tags — rule S1). A report'stargetSurfaceis a surface id optionally followed by its route (UI-01 /orders, orUI-02alone), or a route alone when there is no contract. When the caller names specific behaviors, only those are in scope; otherwise every flow behavior of the surface is.mode(optional) —interactive(default when a user calls) orautonomous(set by implement-feature/evaluator/qa-preflight).test_file_path/profile(any profile the project profile declares) /batch_size(optional; default 4, up to 5).evaluation_report(optional) — itskind: testentry selects the mode: an existingtestFile→ correction mode; atestFilethat does not exist yet, or none → guard mode.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 18d ago Changed · +66 tokens per session 1ec399c02cd6
- 25d ago Changed · +10 lines · -43 tokens per session f584fc193708
- 1mo ago First seen · 142 lines · 172 tokens per session scan A 86ec63353326
e2e-test-writer is a skill published in the GitHub repository dayvisonassis/sdd-skills (3 stars, last pushed 16d ago), licensed MIT. It adds 195 tokens to every session and 3,598 once invoked, about $0.0008 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-30.
Other skills, from other repositories
playwright-expert
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…