e2e-acceptance

e2e-acceptance is a skill for Claude Code, Codex from Justinmendezai/The-Adam-Repo. It costs 87 tokens per session (3,124 once invoked), scanned A, original, Apache-2.0.

A final testing and review workflow for a completed feature after all parts have been merged. It checks the full system, including browser flows when required, APIs, integrations, contracts, and code structure.

In plain words
What is it for?
Use it to run the project's full test suite, Playwright browser checks, API and integration checks, contract checks, and guided quality-assurance scenarios. It can turn confirmed bugs into tests.
Why use it?
It catches problems that may only appear when separately built parts work together. It provides a final check before declaring the project finished or handing it over.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to run the project's full test suite, Playwright browser checks, API and integration checks, contract checks, and guided quality-assurance scenarios. It can turn confirmed bugs into tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinmendezai/the-adam-repo/e2e-acceptance
Install

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.

Any agent
npx skills add Justinmendezai/The-Adam-Repo --skill e2e-acceptance
Clone the repo
git clone --depth 1 https://github.com/Justinmendezai/The-Adam-Repo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for e2e-acceptance

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/e2e-acceptance/github.svg)](https://agentmods.dev/skills/justinmendezai/the-adam-repo/e2e-acceptance)
Your own site
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/e2e-acceptance"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/e2e-acceptance/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.

agentmods 80×15 button for e2e-acceptance

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/e2e-acceptance"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/e2e-acceptance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.03124
Opus 5 $0.00044 $0.01562
Sonnet 5 $0.00017 $0.00625
Haiku 4.5 $0.00009 $0.00312

Measured 12d ago against content hash 13d23864fd92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

e2e-acceptance scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Backend / services:** When the packet includes `verification.layers`, run **api_e2e**, **integration**, and **contract** commands as listed (pytest, Docker stack, OpenAPI checks). **`agentic_qa`** is an orchestrator-
skills/e2e-acceptance/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

e2e-acceptance

The build's final gate. Composes review-via-graph and review-runtime patterns, but at the integration level — the merged main, not a single slice's branch.

  • UI / browser: When packet/PACKET.md includes e2e, runs the Playwright CLI before browser MCP walks. Playwright MCP is for UI depth only — it does not replace FastAPI/pytest/API/scenario coverage.
  • Backend / services: When the packet includes verification.layers, run api_e2e, integration, and contract commands as listed (pytest, Docker stack, OpenAPI checks). agentic_qa is an orchestrator-led pass using the tools in the packet (pytest, curl, docker, DB CLIs, log readers) — do not open a browser unless a scenario truly requires it; convert confirmed bugs into pytest tests.

When to use

  • All slices have merged to main (or the project's integration branch).
  • All per-slice reviews are passing.
  • Right before you declare the project done or hand off to the user.

Not a substitute for per-slice review. This catches integration bugs, not slice-local ones.

Reviewer contract

Every finding raised in this pass (graph review in step 3, agentic_qa in 2c, success-criteria walks in step 4) is held to the same contract as review-via-graph. Restated for the integration level:

  • Pre-report gate (all four "yes"): cite the exact file:line; name the concrete failure mode (input, state, bad outcome); check callers/importers/tests; defensible severity. A critical finding must also explain why existing guards (types, validation, the suite) do not catch it.
  • Skip the noise: framework-handled error paths, validation on internal callers that are already validated, "function too long" for switches/config/test tables, and stylistic preferences that do not violate plan/CONTEXT.md. Pre-existing issues outside this build go to scratch/review-debt.md, not the acceptance report.
  • Zero findings is valid. A clean integration gets approve. Do not manufacture findings to look rigorous.
  • Verdict vocabulary (the machine-readable gate the run-result carries): approve (no critical/warning), warning (warnings only), block (one or more critical). The report's Recommendation line maps directly: approveShip, warningShip or Hold at operator discretion, blockHold for fixes or Escalate.

Read the full file on GitHub · 186 lines

Changes

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.

  1. 12d ago First seen · 186 lines · 0 tokens per session scan A 13d23864fd92

Subscribe to this mod's changes

e2e-acceptance is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 87 tokens to every session and 3,124 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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.

callstack/agent-device · 55 tokens

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.

warpdotdev/warp · 55 tokens

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…

PostHog/posthog-foss · 112 tokens

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.

automateyournetwork/netclaw · 61 tokens

test-loop

Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).

HoangNguyen0403/agent-skills-standard · 25 tokens

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…

testdino-hq/playwright-skill · 64 tokens