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 agentmods add skills/dhaupin/vant/vant-skill-test-e2enpx skills add dhaupin/vant --skill vant-skill-test-e2egit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-test-e2e)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-test-e2e"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-test-e2e.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 | $0.00038 | $0.00355 |
| Opus 5 | $0.00019 | $0.00178 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
test-e2e 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 3d 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.
What it actually says
Test E2E
End-to-end user workflows.
When To Use
- Complete user flows
- Full stack testing
- Customer scenarios
What To Test
1. User Flow
User action → API → Database → UI update
Example: Login → Cart → Checkout → Confirmation
2. Critical Paths
| Path | User Action | Expected |
|---|---|---|
| Signup | Account created | Yes |
| Login | Authenticated | Yes |
| Purchase | Order confirmed | Yes |
| Search | Results shown | Yes |
3. Test Example
test('complete purchase flow', async () => {
await login.valid()
await cart.add(item)
await checkout.pay()
await confirmation.seen()
})
Tools
| Tool | Use |
|---|---|
| Playwright | Browser automation |
| Cypress | E2E testing |
| Puppeteer | Headless Chrome |
| Selenium | Cross-browser |
Output
## E2E Tests
| Flow | Status |
|------|--------|
| Signup | [PASS/FAIL] |
| Login | [PASS/FAIL] |
| Purchase | [PASS/FAIL] |
| Search | [PASS/FAIL] |
Role: E2E Tester
Input: User flow
Output: Test results
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.
- 3d ago First seen · 78 lines · 38 tokens per session scan A 7b3dbbb99505
test-e2e is a skill published in the GitHub repository dhaupin/vant (9 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 355 once invoked, about $0.0002 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-31.
Other skills, from other repositories
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
run-action
Explicit Codex workflow: Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as $rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with…
nav-graph
Explicit Codex workflow: Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
proof-capture
Explicit Codex workflow: Capture PR-ready proof artifacts for a feature, with an attested fail-closed controller in strict mode.
run-workflow
Explicit Codex workflow: Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.