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-validatorWrote 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-validator)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/e2e-test-validator"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/e2e-test-validator/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-validator"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/e2e-test-validator.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.00107 | $0.02582 |
| Opus 5.5 | $0.00043 | $0.01033 |
| Sonnet 5.5 | $0.00021 | $0.00516 |
| Haiku 4.5 | $0.00011 | $0.00258 |
Grade A, and why
e2e-test-validator 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 25d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Validator
Audit end-to-end test files to ensure they comply with every rule the e2e-test-writer
enforces. Read-only: produce a compliance report; never modify test, harness or production
files, never execute tests (static analysis only).
The full rule set is in
../e2e-test-writer/references/e2e-rules.md— validate against it. Build its project profile from the project'sGATES.mdfirst: it says which profiles, folders, test language, fixtures and data policy the rules apply to here.
Scope: the project's e2e test directory. Out of scope, reported as such: the visual suite, and
the harness's own files — the runner config, the global setup, the seed tests, the fixtures module
and any module imported only by them (a sessions helper, say), as the e2e section of GATES.md
names them. A harness-like file shipped with a feature's tests (its own config, global setup,
or a support module shared between spec files) is not out of scope: it is a CRITICAL H2 violation.
INPUT
test_file_path(required) — test file or directory.checklist_file_path(optional) — thee2e-test.mdfor coverage cross-reference; when absent, look fordocs/<feature-id>-*/e2e-test.mdfrom the files' feature tag.contract_path(optional) — the feature'scontract.md, to check that tags name real ids; when absent, look fordocs/<feature-id>-*/contract.mdfrom the feature tag. Ids repeat across features: never check a tag against another feature's contract.severity_filter(optional) —critical|major|minor(default: all).
OUTPUT
A compliance report (English): the project profile it applied (a few lines), summary counts,
overall verdict — PASS = 0 critical and 0 major (minors are listed, not counted against it);
PASS WITH WARNINGS = 0 critical and ≥1 major; FAIL = ≥1 critical — each violation
([SEVERITY] Rule-ID, location, description, expected, found, fix), traceability analysis, and
positive findings. When dispatched, the verdict is the signal the caller consumes.
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.
- 25d ago Changed · +13 lines · -7 tokens per session 1844acdb99f6
- 1mo ago First seen · 93 lines · 114 tokens per session scan A e82ee99b9777
e2e-test-validator is a skill published in the GitHub repository dayvisonassis/sdd-skills (3 stars, last pushed 16d ago), licensed MIT. It adds 107 tokens to every session and 2,582 once invoked, about $0.0004 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…