DeepCode is an open agentic coding system that uses an agent runtime, interactive terminal interface, and desktop workbench to turn research papers and natural-language ideas into code. It is for developers who want goal-driven coding sessions, verification, reusable skills, permissions, and coordinated agents in their repositories. The catalogue entries are skills for its coding workflow.
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 HKUDS/DeepCode --skill webapp-testinggit clone --depth 1 https://github.com/HKUDS/DeepCodeWrote 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/hkuds/deepcode/webapp-testing)<a href="https://agentmods.dev/skills/hkuds/deepcode/webapp-testing"><img src="https://agentmods.dev/badge/skills/hkuds/deepcode/webapp-testing/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/hkuds/deepcode/webapp-testing"><img src="https://agentmods.dev/badge/skills/hkuds/deepcode/webapp-testing.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.00035 | $0.00884 |
| Opus 5.5 | $0.00014 | $0.00354 |
| Sonnet 5.5 | $0.00007 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
webapp-testing 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 1mo 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
- webapp-testing — 100% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Application Testing
To test local web applications, write native Python Playwright scripts.
Helper Scripts Available:
scripts/with_server.py- Manages server lifecycle (supports multiple servers)
Always run scripts with --help first to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.
Decision Tree: Choosing Your Approach
User task → Is it static HTML?
├─ Yes → Read HTML file directly to identify selectors
│ ├─ Success → Write Playwright script using selectors
│ └─ Fails/Incomplete → Treat as dynamic (below)
│
└─ No (dynamic webapp) → Is the server already running?
├─ No → Run: python scripts/with_server.py --help
│ Then use the helper + write simplified Playwright script
│
└─ Yes → Reconnaissance-then-action:
1. Navigate and wait for networkidle
2. Take screenshot or inspect DOM
3. Identify selectors from rendered state
4. Execute actions with discovered selectors
Example: Using with_server.py
To start a server, run --help first, then use the helper:
Single server:
python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
Multiple servers (e.g., backend + frontend):
python scripts/with_server.py \
--server "cd backend && python server.py" --port 3000 \
--server "cd frontend && npm run dev" --port 5173 \
-- python your_automation.py
To create an automation script, include only Playwright logic (servers are managed automatically):
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
page = browser.new_page()
page.goto('http://localhost:5173') # Server already running and ready
page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
# ... your automation logic
browser.close()
What ships with it
5 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.
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.
- 1mo ago First seen · 97 lines · 35 tokens per session scan A 1f77d7de1954
webapp-testing is a skill published in the GitHub repository HKUDS/DeepCode (16,709 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 884 once invoked, about $0.0001 per session on Opus 5.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
browser-qa
A live browser quality-checking workflow that replays user journeys with Playwright-compatible scripts, screenshots, and reports. It stores test cases and run evidence under `.agents/qa/`.
loom-e2e-testing
End-to-end testing for web applications with Playwright, Cypress, Selenium, and Puppeteer.
mstar-e2e
Runs separately requested E2E, real-browser, device, or installed-deployment verification and produces scoped evidence. Loads only for an explicit user request or amazing-e2e-check entry; never from routine QA, UI changes, missing screenshots, or review recommendations.
verify
A local, evidence-based procedure for checking that an implemented feature or bug fix works in the actual app. It uses a browser, test accounts, logs, and screenshots or command output rather than relying only on linting or type checks.
web-e2e
Full end-to-end browser testing for local web apps with a persistent logged-in session. Log in once into a named Chrome profile, then drive real flows with trace evidence against your locally served app - Laravel/Herd, docker compose, FastAPI+SPA, Vite. Adds per-project orchestration via .e2e/config.json - boot +…
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.