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/automata-network/agent-skills/web-test)<a href="https://agentmods.dev/skills/automata-network/agent-skills/web-test"><img src="https://agentmods.dev/badge/skills/automata-network/agent-skills/web-test.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.00033 | $0.12429 |
| Opus 5 | $0.00016 | $0.06215 |
| Sonnet 5 | $0.00007 | $0.02486 |
| Haiku 4.5 | $0.00003 | $0.01243 |
Grade A, and why
web-test 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 5d 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 — 1,387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Test Execution
Execute tests from persistent test cases in ./tests/ directory.
CRITICAL RULES - READ FIRST
Rule 1: Wallet Setup Based on config.yaml
┌────────────────────────────────────────────────────────────────┐
│ IF config.yaml contains: │
│ │
│ web3: │
│ enabled: true │
│ │
│ THEN at TEST START (before any test cases): │
│ │
│ 1. skill web-test-wallet-setup ← REQUIRED AT START! │
│ │
│ Wallet CONNECT is handled by test cases: │
│ │
│ 2. WALLET-001 test case ← Is a TEST CASE │
│ (uses web-test-wallet-connect internally) │
│ │
│ ❌ DO NOT skip wallet-setup for Web3 DApps │
│ ❌ DO NOT auto-run wallet-connect (it's a test case now) │
│ ✅ Run wallet-setup ONCE at start if web3.enabled: true │
│ ✅ Run WALLET-001 test when reached in execution_order │
└────────────────────────────────────────────────────────────────┘
Why this matters:
- Wallet setup prepares the extension (download, import key)
- Wallet connect is now a testable feature (WALLET-001)
- Other tests depend on WALLET-001 via preconditions
Rule 2: NEVER Skip Tests Due to Time Constraints
╔════════════════════════════════════════════════════════════════╗
║ ⛔ CRITICAL RULE ⛔ ║
╠════════════════════════════════════════════════════════════════╣
║ ║
║ This is AUTOMATED TESTING - user does NOT care about time! ║
║ Run ALL tests, no matter how long it takes. ║
║ ║
║ ❌ FORBIDDEN - These excuses are NOT allowed: ║
║ - "Time constraints" ║
║ - "To save time" ║
║ - "Already running too long" ║
║ - "Similar to another test" ║
║ - "Will test later" ║
║ - "Not enough time" ║
║ ║
║ ✅ VALID reasons to skip a test: ║
║ - User requested specific tests (see Selective Execution) ║
║ Example: "Run only SWAP-001" → skip other tests ║
║ - User requested specific module/feature ║
║ Example: "Run wallet module" → skip non-wallet tests ║
║ - Blocking dependency failed (depends_on test failed) ║
║ - Feature does not exist in the project ║
║ - Test case is explicitly deprecated ║
║ ║
║ ⚠️ IF YOU SKIP A TEST FOR "TIME CONSTRAINTS": ║
║ → The test run is considered INCOMPLETE ║
║ → User will NOT accept the results ║
║ → You MUST re-run the skipped tests ║
║ ║
╚════════════════════════════════════════════════════════════════╝
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- package-lock.json 1.8 KB
- package.json 501 B
- references/CHECKLIST.md 4.7 KB
- references/ELEMENT-TYPES.md 6.5 KB
- references/REFERENCE.md 8.0 KB
- scripts/commands/basic.js 17 KB runs code
- scripts/commands/dev-server.js 6.0 KB runs code
- scripts/commands/login.js 10 KB runs code
- scripts/commands/network.js 14 KB runs code
- scripts/commands/vision.js 3.9 KB runs code
- scripts/lib/browser.js 13 KB runs code
- scripts/lib/config.js 2.9 KB runs code
- scripts/lib/scheduler.js 8.3 KB runs code
- scripts/lib/utils.js 6.6 KB runs code
- scripts/lib/wallet-utils.js 9.4 KB runs code
- scripts/test-helper.js 6.6 KB runs code
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.
- 5d ago First seen · 1,387 lines · 33 tokens per session scan A 0a8994640e47
web-test is a skill published in the GitHub repository automata-network/agent-skills (1 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 12,429 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…