Borrowing it
Nothing to install: this file belongs to ddebixx/frontend-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ddebixx/frontend-template/main/.cursor/skills/acceptance-verification/SKILL.mdgit clone --depth 1 https://github.com/ddebixx/frontend-templateWrote 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/ddebixx/frontend-template/acceptance-verification)<a href="https://agentmods.dev/skills/ddebixx/frontend-template/acceptance-verification"><img src="https://agentmods.dev/badge/skills/ddebixx/frontend-template/acceptance-verification/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/ddebixx/frontend-template/acceptance-verification"><img src="https://agentmods.dev/badge/skills/ddebixx/frontend-template/acceptance-verification.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.00100 | $0.00735 |
| Opus 5.5 | $0.00040 | $0.00294 |
| Sonnet 5.5 | $0.00020 | $0.00147 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
acceptance-verification 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 16d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance verification
Verification is a separate phase from implementation. During the verification pass, inspect and test; do not fix the code you are judging.
Workflow
-
Locate the contract
- Read the approved specification, implementation plan, relevant project rules, and changed code.
- If no specification or testable acceptance criteria exist for non-trivial work, return
BLOCKED: missing verification contractrather than inventing criteria after the fact.
-
Establish the change surface
- Identify changed files, public interfaces, user flows, data/state changes, dependencies, and likely regression areas.
- Note any implementation behavior not represented in the spec.
-
Create the acceptance matrix
- Use references/verification-report-template.md.
- Map every
mustacceptance criterion to concrete evidence. - Do not treat one passing test suite as proof of unrelated criteria.
-
Run appropriate project checks
- Inspect existing package scripts, CI configuration, and test conventions before choosing commands.
- Run relevant build, typecheck, lint, unit, integration, or E2E checks when available.
- Do not invent commands or tools that are not configured.
- Record command and result summaries as evidence.
-
Verify behavior, not only code shape
- For UI work, inspect the rendered interface when browser tooling is available.
- Exercise relevant happy paths and negative paths.
- Check loading, empty, error, permission, long-content, responsive, keyboard, and reduced-motion states when required by the spec.
- For APIs/data flows, verify inputs, outputs, validation, failure handling, compatibility, and persistence semantics where applicable.
-
Check for regressions and scope leakage
- Look for unintended behavior changes outside the specified scope.
- Flag hidden coupling, stale code paths, missing cleanup, broken tests, incompatible contracts, or new behavior without specification coverage.
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.
- 16d ago First seen · 63 lines · 100 tokens per session scan A f3e8c12c4b73
acceptance-verification is a skill published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 17d ago), licensed MIT. It adds 100 tokens to every session and 735 once invoked, about $0.0004 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-13.
Other skills, from other repositories
test-conversion-reviewer
Reviewer for converting unit tests to browser tests for Project Bedrock. Invoke this when the user needs to review their work while removing complex Browser dependencies from tests.
ln-51-acceptance-test-builder
Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.
test-case-coverage
Audits an already-automated test case (TC-XXX) — one end-to-end journey across several use cases — against its document and reports a coverage matrix: which Flow rows, Validation items, and postconditions have a test step and code behind them, which are still open, and which test steps have drifted away from the test…
triaging-visual-review-runs
Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", "quarantine", asks why a PR is blocked or what changed visually, wants to triage the VR…
full-stack-e2e-review
Run a rigorous end-to-end product or feature review across architecture, data, APIs, permissions, billing, tests, and real browser UX. Use for requests such as review this branch end to end, test everything, ensure no bugs, perform a full visual pass, or validate a multi-user workflow before merge or deploy.
review
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".