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/miniapp-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/miniapp-accept)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/miniapp-accept"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/miniapp-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.00027 | $0.00607 |
| Opus 5 | $0.00014 | $0.00303 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
miniapp-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 4d 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
Miniapp Accept（流程入口）
运行时边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md
输入契约
- 任务名或 feature 名
- 相关设计文档（如适用）：
.ai/design/[任务名].md - miniapp 变更文件或上游 handoff
输出契约
- 质量报告：
.ai/quality/check-[date].md - 验收结论：
ACCEPTED/REJECTED/ACCEPTED_WITH_IMPROVEMENTS - 重复代码检查结果：必须写入报告，包含执行命令、重复率/重复块数量、关键文件位置；未执行时必须说明原因
- 每条结论都必须包含证据文件或命令输出来源
执行流程
步骤 0：设计一致性检查（MANDATORY）
- 读取
.ai/design/[任务名].md - 根据豁免前缀判断是否可跳过
步骤 1：基础质量命令
- 运行
typecheck、build:weapp - 执行重复代码扫描并保留报告证据
- 按需运行
build:h5、prepublish:check、starter:ci-gate - 收集类型、构建和模板门禁失败证据
步骤 2：技术线与模板约束检查
- 检查页面注册、token/theme/icon 规则
- 检查是否引入禁用依赖或绕过
AppIcon
步骤 3：输出报告
- 输出到
.ai/quality/check-[date].md - 给出状态：
ACCEPTED/REJECTED/ACCEPTED_WITH_IMPROVEMENTS
规范来源
验收标准、检查清单、通过/拒绝规则、报告字段参考：
${CLAUDE_PLUGIN_ROOT}/guides/miniapp/quality.md
若目标仓库未提供该规范，则以本文件中的流程、检查项和实际仓库证据作为最小验收标准，并在报告中标记"外部规范缺失"。
具体检查项以 ${CLAUDE_PLUGIN_ROOT}/guides/miniapp/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.
- 4d ago First seen · 64 lines · 27 tokens per session scan A 8045aeae6137
miniapp-accept is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 607 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-08-30.
Other agents, from other repositories
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…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.