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.
npx skills add Justinmendezai/The-Adam-Repo --skill e2e-acceptancegit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/e2e-acceptance)<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.
<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>- NVIDIA SkillSpector pass
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.00087 | $0.03124 |
| Opus 5.5 | $0.00035 | $0.01250 |
| Sonnet 5.5 | $0.00017 | $0.00625 |
| Haiku 4.5 | $0.00009 | $0.00312 |
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 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.
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- 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.mdincludese2e, 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_qais 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. Acriticalfinding 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 toscratch/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(nocritical/warning),warning(warnings only),block(one or morecritical). The report's Recommendation line maps directly:approve→Ship,warning→ShiporHoldat operator discretion,block→Hold for fixesorEscalate.
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 · 186 lines · 0 tokens per session scan A 13d23864fd92
e2e-acceptance is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (14 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 3,124 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
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…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.