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 ryanzhao1011/workframe --skill acceptance-criteriagit clone --depth 1 https://github.com/ryanzhao1011/workframeWrote 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/ryanzhao1011/workframe/acceptance-criteria)<a href="https://agentmods.dev/skills/ryanzhao1011/workframe/acceptance-criteria"><img src="https://agentmods.dev/badge/skills/ryanzhao1011/workframe/acceptance-criteria.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.1 | $0.00036 | $0.01568 |
| Opus 5 | $0.00018 | $0.00784 |
| Sonnet 5 | $0.00007 | $0.00314 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
acceptance-criteria 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
验收标准编写技能
格式选择
根据验收内容选择合适的格式：
| 格式 | 适用场景 | 示例 |
|---|---|---|
| GWT 场景式 | 用户行为场景、操作流、交互逻辑 | 用户点击提交按钮后的响应 |
| 规则式清单 | 业务约束、配置规则、数据校验、合规要求 | 密码强度规则、字段长度限制 |
同一 Story 允许两种格式混合使用。
GWT 场景式格式
AC-{序号}: {标准名称}
Given {前置条件/上下文}
And {补充条件}（可选）
When {用户操作/系统事件}
Then {预期结果/系统响应}
And {补充结果}（可选）
编写规范
- 每条 AC 只允许一个 When/Then 对（防止 AC 过于宽泛）
- 使用主动语态（"系统显示提示信息" 而非 "提示信息被系统显示"）
- 避免 "not" 否定句（用正面描述替代："按钮置灰不可点击" → "按钮处于禁用状态"）
- 使用简单句，不用从句嵌套
- 条件和结果必须可量化或可观测
GWT 示例
AC-01: 成功提交任务
Given 用户已登录且剩余使用次数 ≥ 1
And 用户已完成必填配置项
When 用户输入内容并点击"提交"
Then 系统在 60 秒内返回处理结果
And 用户剩余使用次数减少 1
AC-02: 使用次数不足时的操作限制
Given 用户已登录且剩余使用次数为 0
When 用户访问功能页面
Then "提交"按钮处于禁用状态
And 页面显示提示"使用次数已用完，请升级套餐"
And 显示套餐升级入口链接
规则式清单格式
AC-{序号}: {规则名称}
规则：
- [ ] {规则1}
- [ ] {规则2}
- [ ] {规则3}
规则式示例
AC-03: 文章输入校验规则
规则：
- [ ] 原文字数不少于 100 字
- [ ] 原文字数不超过 50,000 字
- [ ] 不接受纯图片/纯链接内容
- [ ] 输入内容自动过滤 HTML 标签
- [ ] 检测到敏感词时阻止提交并提示具体原因
复杂度分级数量标准
根据 Story 规模确定最少 AC 数量：
| Story 规模 | 最少 AC 数量 | 说明 |
|---|---|---|
| 1-2 Story Points | 3-4 条 | 正常路径 + 1-2 个异常路径 |
| 3-5 Story Points | 4-6 条 | 正常路径 + 多个异常/边界场景 |
| 8 Story Points | 5-8 条 | 全面覆盖，含并发和状态边界 |
| 13+ Story Points | 先拆分 Story | Story 过大，不直接写 AC |
边界条件覆盖清单
每个功能须评估以下 5 类边界条件，按需编写对应 AC：
输入边界
| 条件 | 测试内容 | AC编号 |
|---|---|---|
| 空值 | 输入为空时的处理 | |
| 最小值 | 最小有效输入 | |
| 最大值 | 最大有效输入（如文章字数上限） | |
| 非法格式 | 特殊字符、SQL 注入、XSS | |
| 超长输入 | 超过最大长度限制 |
权限边界
| 条件 | 测试内容 | AC编号 |
|---|---|---|
| 未登录 | 未认证用户访问 | |
| 无权限 | 角色权限不足 | |
| 过期会话 | Token 过期后操作 |
并发边界
| 条件 | 测试内容 | AC编号 |
|---|---|---|
| 重复提交 | 快速连续点击 | |
| 并发修改 | 多人同时编辑同一资源 | |
| 资源竞争 | 任务队列满时的处理 |
状态边界
| 条件 | 测试内容 | AC编号 |
|---|---|---|
| 初始状态 | 首次使用时的默认值 | |
| 中间状态 | 任务处理中的操作限制 | |
| 终态 | 已完成/已取消后的操作限制 | |
| 异常状态 | 网络断开/服务不可用 |
无障碍边界
| 条件 | 测试内容 | AC编号 |
|---|---|---|
| 键盘导航 | Tab 键可遍历所有交互元素 | |
| 屏幕阅读器 | 关键操作有 ARIA 标签 |
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 · 160 lines · 36 tokens per session scan A a8a61e69615c
acceptance-criteria is a skill published in the GitHub repository ryanzhao1011/workframe (4 stars, last pushed 21d ago), licensed MIT. It adds 36 tokens to every session and 1,568 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
html-prototype
A method for creating single-file HTML mockups that open in a browser and follow a project's design tokens, such as its fonts, colours, spacing, corners, and shadows.
feature-acceptance
A browser-based acceptance testing process that compares an online implementation with a product requirements document and, when available, an HTML prototype. It records what is complete, partial, missing, or inconsistent, with screenshots and prioritized blockers.
prd
A skill for writing and reviewing product requirements documents, or PRDs: documents that describe what a product or feature should do. It covers structure, fields, rules, edge cases, metrics, page layouts, and related system or algorithm flows.
gbg
Convert any plan, PRD, feature idea, or brief into a sequenced goal-by-goal execution document with reviewer-gated commits — for everyday feature development, MVPs, migrations, refactors, and hardening alike. Generates a project brief, per-goal scope/tasks/acceptance criteria, an LLM-reviewer prompt (Codex/etc.), a…
ui-walkthrough
A UI comparison skill that checks a design HTML file against a live webpage at the same screen size and state. It reads computed styles, the actual values applied by the browser, to document differences in layout, components, colors, fonts, corners, icons, and spacing.
competitor-research
A skill for maintaining documents about competing products and AI research. It covers product features, agent modules, and framework comparisons, with rules for organizing facts, judgments, screenshots, and follow-up items.