Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/jh941213/codex-lattice/e2e-verify)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/e2e-verify"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/e2e-verify.svg" alt="Measured on agentmods" 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.00079 | $0.01030 |
| Opus 5 | $0.00039 | $0.00515 |
| Sonnet 5 | $0.00016 | $0.00206 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
e2e-verify 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 6d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E 피처 검증
개발 + /verify 완료 후, 구현한 피처가 실제 브라우저에서 동작하는지 E2E 테스트로 검증합니다.
전제 조건
/verify통과 완료 (typecheck, lint, test, build)- 앱이 로컬에서 실행 가능한 상태
워크플로우
1단계: 피처 분석
구현한 피처의 사용자 플로우를 파악합니다.
- 어떤 페이지에서 시작하는가?
- 어떤 인터랙션이 필요한가? (클릭, 입력, 네비게이션)
- 성공 조건은 무엇인가? (URL 변경, 텍스트 표시, 상태 변화)
- 엣지 케이스는? (빈 입력, 에러 응답)
2단계: 앱 실행
# package.json에서 dev/start 스크립트 확인
cat package.json | grep -A 5 '"scripts"'
# 앱 실행 (백그라운드)
npm run dev &
sleep 5 # 앱 준비 대기
3단계: E2E 테스트 작성
e2e/ 디렉토리에 테스트 파일 생성합니다.
# 프로젝트에 기존 E2E 설정 확인
ls e2e/ 2>/dev/null || ls tests/e2e/ 2>/dev/null || ls __tests__/e2e/ 2>/dev/null
# 기존 E2E 프레임워크 확인 (Playwright, Cypress, agent-browser)
cat package.json | grep -E "playwright|cypress|agent-browser"
프레임워크별 테스트 작성
agent-browser 사용 시:
#!/bin/bash
set -e
cleanup() { agent-browser close 2>/dev/null || true; }
trap cleanup EXIT
agent-browser open http://localhost:3000
# 스냅샷으로 요소 확인
agent-browser snapshot -i
# 피처 플로우 실행
agent-browser fill @email-input "[email protected]"
agent-browser click @submit-btn
agent-browser wait text "Success"
echo "PASS: Feature E2E test"
Playwright 사용 시:
import { test, expect } from '@playwright/test';
test('피처명: 사용자 플로우', async ({ page }) => {
await page.goto('/');
await page.fill('[data-testid="email"]', '[email protected]');
await page.click('[data-testid="submit"]');
await expect(page.locator('.success')).toBeVisible();
});
Cypress 사용 시:
describe('피처명', () => {
it('사용자 플로우를 완료한다', () => {
cy.visit('/');
cy.get('[data-testid="email"]').type('[email protected]');
cy.get('[data-testid="submit"]').click();
cy.contains('Success').should('be.visible');
});
});
4단계: 테스트 실행
# agent-browser
bash e2e/test_feature.sh
# Playwright
npx playwright test e2e/feature.spec.ts
# Cypress
npx cypress run --spec "cypress/e2e/feature.cy.ts"
5단계: 실패 시 디버깅
# 스크린샷 캡처
agent-browser screenshot ./e2e/debug.png
# headed 모드로 재실행
agent-browser open http://localhost:3000 --headed
# 콘솔 에러 확인
agent-browser console --error
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.
- 6d ago First seen · 131 lines · 79 tokens per session scan A 1423abe07cf8
e2e-verify is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,030 once invoked, about $0.0004 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.
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.