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 agents/timzaak/web-dev-skills/web-demo-acceptgit clone --depth 1 https://github.com/timzaak/web-dev-skillsWrote 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/agents/timzaak/web-dev-skills/web-demo-accept)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/web-demo-accept"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/web-demo-accept.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.00066 | $0.00961 |
| Opus 5 | $0.00033 | $0.00481 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
web-demo-accept 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.
What it actually says
Demo Accept（流程入口）
运行时边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md
需求来源边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md
输入契约
- 目标测试文件、角色或
all - 相关用户故事路径（
.ai/user-stories/...draft 或docs/user-stories/...已发布文档） - 相关日志和测试结果目录
输出契约
- 单文件报告：
.ai/quality/web-demo-accept-[feature]-[YYYYMMDD-HHMMSS].md - 批量汇总：
.ai/quality/web-demo-accept-summary-[YYYYMMDD-HHMMSS].md - 验收结论：
ACCEPTED/REJECTED/ACCEPTED_WITH_IMPROVEMENTS - 短报告：门禁摘要、P0/P1/P2 单行清单、日志路径
- 重复代码检查：1 行摘要；未执行时说明原因
- 每条问题必须附带文件、日志或命令证据
执行流程
阶段 1：用户故事一致性检查（MANDATORY）
- 识别测试文件对应用户故事
- 校验用户故事路径存在，允许
.ai/user-storiesdraft 和docs/user-storiespublished 两类来源 - 校验场景、角色、断言匹配
阶段 2：编译验证（MANDATORY）
- 执行 demo 编译
- 记录编译错误
阶段 3：执行验证（MANDATORY）
- 执行 demo 测试
- 记录失败、超时、日志位置
阶段 4：代码质量检查
- 检查隔离、日志系统、延迟、选择器、等待模式
- 执行重复代码扫描并保留报告证据
- 检查选择器是否符合
${CLAUDE_PLUGIN_ROOT}/guides/web-demo/selector-strategy.md标准 - 检查 Page Object 使用是否符合
${CLAUDE_PLUGIN_ROOT}/guides/web-demo/pom-guide.md规范 - 检查测试数据构造方式（MANDATORY）
- 验证不使用
api-test-data.helpers.ts - 验证不使用
db-test-data.helpers.ts - 验证不使用
subscription-creation.helpers.ts - 验证所有业务数据使用 Demo Seed 或用户端 UI 操作
- 验证不进行管理端 UI 操作
- 验证不使用
阶段 5：覆盖率验证
- 计算场景覆盖率
- 判定是否达标
阶段 6：输出报告
- 单文件报告：
.ai/quality/web-demo-accept-[feature]-[YYYYMMDD-HHMMSS].md - 批量验收输出汇总报告
规范来源
插件内置参考：
${CLAUDE_PLUGIN_ROOT}/guides/web-demo/index.md— Demo guide 入口${CLAUDE_PLUGIN_ROOT}/guides/web-demo/selector-strategy.md— 选择器策略标准${CLAUDE_PLUGIN_ROOT}/guides/web-demo/pom-guide.md— POM 模式规范${CLAUDE_PLUGIN_ROOT}/guides/web-demo/test-maintenance.md— 测试可维护性标准
Runtime Dependencies： 验收标准、评分公式、拒绝条件、报告模板参考：
${CLAUDE_PLUGIN_ROOT}/guides/web-demo/quality.md
若目标仓库未提供该规范，则以本文件中的流程、质量门禁和实际仓库证据作为最小验收标准，并在报告中标记“外部规范缺失”。
执行限制
- ❌ 未经授权不得修改代码
- ✅ 每条结论必须标明文件来源
- ❌ 禁止空泛建议
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 · 90 lines · 66 tokens per session scan A 8c2d85ebf77a
web-demo-accept is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 961 once invoked, about $0.0003 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-30.
Other agents, from other repositories
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
qa-engineer
Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…