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 weapp-vite/weapp-vite --skill weapp-acceptancegit clone --depth 1 https://github.com/weapp-vite/weapp-viteWrote 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/weapp-vite/weapp-vite/weapp-acceptance)<a href="https://agentmods.dev/skills/weapp-vite/weapp-vite/weapp-acceptance"><img src="https://agentmods.dev/badge/skills/weapp-vite/weapp-vite/weapp-acceptance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/weapp-vite/weapp-vite/weapp-acceptance"><img src="https://agentmods.dev/badge/skills/weapp-vite/weapp-vite/weapp-acceptance.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00529 |
| Opus 5.5 | $0.00020 | $0.00212 |
| Sonnet 5.5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
weapp-acceptance 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 15d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- weapp-acceptance — 100% identical, 0 lines differ
What it actually says
Weapp acceptance
Keep planning and code edits in the host agent. Weapp Agent executes checks and collects evidence; it does not need another model or API key.
- Call
weapp_project_inspectwhen available, orwv accept <project> --inspect --json. Limit acceptance claims to supported weapp-vite native/Wevu projects on WeChat. - Maintain
acceptance.scenariosinweapp-acceptance.config.jsonfor the requested behavior. Read scenarios.md when creating or changing a scenario. Preserve unrelated checks and user changes. Choose assertions from the requested outcome, not from whichever output the current code produces. - Start
weapp_acceptance_start, retain itsjobId, and queryweapp_acceptance_statusuntil it is no longerrunning. Use CLIwv accept <project> --jsonif MCP is unavailable; CLI waits for completion. Do not launch duplicate jobs to poll progress. - Read
weapp_acceptance_reportand relevant named artifacts. Repair the cause of failures within the user's task, then run a new acceptance job. Repeated environment failures require resolving the stated prerequisite, not repeated navigation or input.
Honor existing host authorization. A tool's action_required result does not authorize silently adding --trust. Explain the concrete scripts/configuration that need review. Scenario edits invalidate the stored trust decision. Never lower required checks, delete assertions, or replace actual values with expected values to obtain a pass.
Reports use version: 2. Claim acceptance passed only when passed is true and snapshot.stale is false; state the report's requiredChecks. Build-only acceptance is not runtime verification. verify --json is the legacy command report and is not a full acceptance verdict.
Report failures, missing evidence, and environment blockers distinctly. Screenshots support inspection but do not prove visual correctness. runtime: wechat-devtools describes the developer-tool simulator, not a physical device. Interrupted tasks are not replayed: inspect the last recorded step and current state before starting a fresh job.
When reporting completion, provide the job ID, checks performed, failed/unverified categories, and relevant screenshot/log artifacts. Do not claim a runtime action occurred unless the report records it.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago First seen · 22 lines · 51 tokens per session scan A b1d7a52d506d
weapp-acceptance is a skill published in the GitHub repository weapp-vite/weapp-vite (514 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 529 once invoked, about $0.0002 per session on Opus 5.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-10-01.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
playwright-page-objects
Use when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.
test-building-blocks
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…
add-redirect
Add or update URL redirects in the server redirect registry, with status-code rationale and E2E coverage.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…