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/backend-acceptgit clone --depth 1 https://github.com/timzaak/web-dev-skillsWhat 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.00065 | $0.00830 |
| Opus 5 | $0.00032 | $0.00415 |
| Sonnet 5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
backend-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 3d 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
Backend Accept（流程入口）
运行时边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md
输入契约
- 任务名或 feature 名
- 相关设计文档：
.ai/design/[任务名].md - 上游 handoff 与后端改动范围
输出契约
- 报告：
.ai/quality/backend-accept-[feature]-[YYYYMMDD-HHMMSS].md - 验收结论：
ACCEPTED/REJECTED/ACCEPTED_WITH_IMPROVEMENTS - 短报告：门禁摘要、P0/P1/P2 单行清单、证据路径
- 重复代码检查：1 行摘要；未执行时说明原因
- handoff：明确 backend 阶段是否可进入后续 frontend/demo 阶段
执行流程
步骤 0：设计一致性检查（MANDATORY）
- 读取
.ai/design/[任务名].md - 根据豁免前缀判断是否可跳过
步骤 1：基础质量命令
- 先分析改动范围与上游 handoff，再执行编译与定向测试命令
- 执行重复代码扫描并保留报告证据
- 收集失败证据与日志
- 默认不直接运行全量
uv run scripts/backend-test.py -- - 仅在用户明确要求全量测试，或影响范围无法可靠收敛时，才升级为全量测试
步骤 2：环境验证（MANDATORY）
- 启动环境
- 执行健康检查
- 清理环境
步骤 3：OpenAPI 验证
- 检查 utoipa 注解
- 检查 ToSchema
- 检查 ApiDoc 注册和导出产物
- 执行 OpenAPI 导出，并验证
frontend/api.json有效 - 执行前端 API 客户端生成命令，并记录生成结果
- 允许运行目标项目的 OpenAPI/API client 生成命令来取得验收证据；除此之外不得修改业务代码
步骤 4：输出报告
- 输出到
.ai/quality/backend-accept-[feature]-[YYYYMMDD-HHMMSS].md - 给出状态：
ACCEPTED/REJECTED/ACCEPTED_WITH_IMPROVEMENTS - 明确 OpenAPI 导出、前端 API 生成、测试和环境验证是否均已通过，并给出下一阶段 handoff
规范来源
验收标准、检查清单、通过/拒绝规则、报告字段参考：
${CLAUDE_PLUGIN_ROOT}/guides/backend/index.md${CLAUDE_PLUGIN_ROOT}/guides/backend/quality.md
若目标仓库未提供该规范，则以本文件中的流程、最小测试证据和 OpenAPI 检查结果作为最小验收标准，并在报告中标记“外部规范缺失”。
执行限制
- ❌ 未经授权不得修改代码
- ✅ 每条结论必须标明文件来源
- ❌ 禁止空泛建议
- ❌ 禁止把全量
uv run scripts/backend-test.py --当作backend-accept的默认步骤
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.
- 3d ago First seen · 79 lines · 65 tokens per session scan A baa560ede8fe
backend-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 65 tokens to every session and 830 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
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
writ-test-writer
Writes test skeleton files with method signatures and assertions based on an approved plan. Use after plan approval, before implementation.
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…