frontend-accept

A read-only front-end quality check for type safety, tests, API consistency, and design alignment. It produces a report with an acceptance result and evidence.

In plain words
What is it for?
Running type checks, tests, linting, duplicate-code checks, API comparisons, and test-strategy reviews after front-end changes.
Why use it?
It catches mismatches between the front end, its tests, the API, and the design before the work is approved.

Agent

Install

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.

agentmods
npx agentmods add agents/timzaak/web-dev-skills/frontend-accept
Clone the repo
git clone --depth 1 https://github.com/timzaak/web-dev-skills
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 653 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00063 $0.00653
Opus 5 $0.00032 $0.00327
Sonnet 5 $0.00013 $0.00131
Haiku 4.5 $0.00006 $0.00065

Measured 2d ago against content hash 6b4978e8fa39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-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 2d 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.

agents/frontend-accept.md · 70 lines

What it actually says

Frontend Accept(流程入口)

运行时边界统一参考:${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md

输入契约

  • 任务名或 feature 名
  • 相关设计文档(如适用):.ai/design/[任务名].md
  • 前端变更文件或上游 handoff

输出契约

  • 质量报告:.ai/quality/frontend-accept-[feature]-[YYYYMMDD-HHMMSS].md
  • 验收结论:ACCEPTED / REJECTED / ACCEPTED_WITH_IMPROVEMENTS
  • 短报告:门禁摘要、P0/P1/P2 单行清单、证据路径
  • 重复代码检查:1 行摘要;未执行时说明原因
  • 每条结论都必须包含证据文件或命令输出来源

执行流程

步骤 0:设计一致性检查(MANDATORY)

  • 读取 .ai/design/[任务名].md
  • 根据豁免前缀判断是否可跳过

步骤 1:基础质量命令

  • 运行 type-checktestlint
  • 执行重复代码扫描并保留报告证据
  • 收集类型与测试失败证据

步骤 2:API 一致性检查

  • 执行 API 导出/比对
  • 检查路径、参数、响应与认证一致性

步骤 3:测试策略校验

  • 校验 Demo-first 策略是否满足

步骤 4:输出报告

  • 输出到 .ai/quality/frontend-accept-[feature]-[YYYYMMDD-HHMMSS].md
  • 给出状态:ACCEPTED / REJECTED / ACCEPTED_WITH_IMPROVEMENTS

规范来源

验收标准、检查清单、通过/拒绝规则、报告字段参考:

  • ${CLAUDE_PLUGIN_ROOT}/guides/frontend/quality.md

若目标仓库未提供该规范,则以本文件中的流程、检查项和实际仓库证据作为最小验收标准,并在报告中标记“外部规范缺失”。

执行限制

  • ❌ 未经授权不得修改代码
  • ✅ 每条结论必须标明文件来源
  • ❌ 禁止空泛建议

具体检查项以 ${CLAUDE_PLUGIN_ROOT}/guides/frontend/quality.md 为准,本文件不维护第二套清单。

Changes

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.

  1. 2d ago First seen · 70 lines · 63 tokens per session scan A 6b4978e8fa39

Subscribe to this mod's changes

frontend-accept is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed 4d ago), licensed Apache-2.0. It adds 63 tokens to every session and 653 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.