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-research)<a href="https://agentmods.dev/skills/automata-network/agent-skills/web-test-research"><img src="https://agentmods.dev/badge/skills/automata-network/agent-skills/web-test-research/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/automata-network/agent-skills/web-test-research"><img src="https://agentmods.dev/badge/skills/automata-network/agent-skills/web-test-research.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.04868 |
| Opus 5 | $0.00018 | $0.02434 |
| Sonnet 5 | $0.00007 | $0.00974 |
| Haiku 4.5 | $0.00004 | $0.00487 |
Grade A, and why
web-test-research 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 8d 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 — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Research
Analyze any web project to understand what it does and what needs to be tested.
Core Principle: Full Code Tree Traversal + Visual Analysis
╔════════════════════════════════════════════════════════════════╗
║ ⚠️ CRITICAL: FULL CODE TREE TRAVERSAL ║
╠════════════════════════════════════════════════════════════════╣
║ ║
║ You MUST read the ENTIRE codebase systematically: ║
║ ║
║ 1. Start from entry files (index.ts, main.ts, App.tsx) ║
║ 2. Follow ALL imports/references like a tree ║
║ 3. Read EVERY file that is referenced ║
║ 4. Build a complete module & function map ║
║ ║
║ DO NOT: ║
║ ✗ Only search for specific keywords ║
║ ✗ Only read files you think are important ║
║ ✗ Skip files because they "look simple" ║
║ ✗ Miss functionality hidden in utility files ║
║ ║
║ The goal is 100% code coverage understanding! ║
║ ║
╚════════════════════════════════════════════════════════════════╝
You must dynamically:
- Detect - Is this a Web3 DApp? What dependencies does it use?
- Find Docs - Read README.md, design docs, architecture docs for requirements
- Tree Traverse - Start from entry files, read EVERY imported file
- Map Modules - Build complete module map with entry files
- Research - WebSearch any unknown dependency/protocol
- See - Launch the app and take UI screenshots to discover visual features
- Analyze Business - Deep dive into business logic, user flows, roles, and permissions
- Generate - Create comprehensive feature analysis for test case generation
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.
- 8d ago First seen · 617 lines · 36 tokens per session scan A 43a9949e1327
web-test-research is a skill published in the GitHub repository automata-network/agent-skills (1 stars, last pushed 8mo ago), licensed MIT. It adds 36 tokens to every session and 4,868 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
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.
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.
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…
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.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
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…