Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add timzaak/web-dev-skills/plugin install t-toolsWrote 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/timzaak/web-dev-skills/t-web-demo-run)<a href="https://agentmods.dev/skills/timzaak/web-dev-skills/t-web-demo-run"><img src="https://agentmods.dev/badge/skills/timzaak/web-dev-skills/t-web-demo-run/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/timzaak/web-dev-skills/t-web-demo-run"><img src="https://agentmods.dev/badge/skills/timzaak/web-dev-skills/t-web-demo-run.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.00029 | $0.00521 |
| Opus 5 | $0.00015 | $0.00260 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
t-web-demo-run 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 today.
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
Chrome 扩展 Demo 的 fixture、--no-auto-env 参数传递、修复后重建和批次隔离按 ${CLAUDE_PLUGIN_ROOT}/protocols/web-demo-run-repair-contract.md 的“扩展 Demo 运行模式”；仅此模式下不执行默认 Web 环境 stop/start。
单文件 Demo 测试运行与修复
运行时边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md
单文件运行与修复闭环（整文件 → 拆用例 → 诊断 → 分发修复 → 补测 → 整文件终验，含环境重建、run ID 和结果字段规则）统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/web-demo-run-repair-contract.md
使用方式
/t-tools:t-web-demo-run demo/e2e/<role>/<scenario>.e2e.ts
执行流程
- 校验参数：测试文件必须存在且扩展名为
.e2e.ts；单次执行只处理一个测试文件。 - 按
web-demo-run-repair-contract.md的单文件执行顺序处理整文件运行、失败用例修复、补测和整文件终验。 - 用 Task 记录当前失败用例和尝试轮次，供中断后继续。
- 最后一行仅输出该协议定义的
Result: {...}。
恢复机制
当流程中断时：
- 读取
TaskList。 - 按任务列表顺序找到第一个
pending或failed任务继续执行。
失败处理
- 环境启动失败：停止并记录错误。
- 无可用修复方案：标记该用例失败，继续下一个。
- 达到最大重试次数：标记失败并继续。
- 补测失败：记录失败与风险，不阻断本用例修复循环，继续 Demo 重跑与后续尝试。
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.
- today Changed · +3 lines 0d0ae66e20b6
- 5d ago Changed · -13 lines 011345acf841
- 6d ago First seen · 62 lines · 29 tokens per session scan A a96035124ce2
t-web-demo-run is a skill published in the GitHub repository timzaak/web-dev-skills (74 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 521 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
azure-playwright-workspaces
Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or run/AADSTS7000112 issues, and other Playwright Workspaces related…
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…