A verification workflow for checking completed feature, bug, interface, API, mobile, security, or deployment work against acceptance criteria. It records evidence from the relevant checks.

Use it to select appropriate unit, integration, end-to-end, mobile, security, migration, or deployment checks and document their results.

It helps teams prove that delivered work meets its stated requirements before handoff.

verify-work — Skill for Codex by HoangNguyen0403/agent-skills-standard

Install

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.

Any agent

npx skills add HoangNguyen0403/agent-skills-standard --skill verify-work

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-work/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-work)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-work"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-work/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/verify-work"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/verify-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.01102
Opus 5.5	$0.00009	$0.00441
Sonnet 5.5	$0.00005	$0.00220
Haiku 4.5	$0.00002	$0.00110

Measured 12d ago against content hash 82d89d0e4012, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-work 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 12d 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.

.codex/skills/verify-work/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Work Skill

[!IMPORTANT] Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Instructions

When the user asks to perform this workflow, execute the following steps:

Verify Work Workflow

Goal: Prove the delivered change works against explicit acceptance criteria before handoff.

Load the approved brief/acceptance criteria and changed files; use inherited operator_profile and risk tier. Preserve sensitive minimum medium risk (high when required); require PRD/SRS trace only for governed work.
Select applicable unit/component, integration/API, E2E/visual, mobile, security, migration, and deployment-smoke lanes.
Run smallest reliable checks first. Use Playwright/Appium only for changed user behavior; run driver scripts/preflight.sh and use first available rung (web: CLI then MCP; mobile: local then cloud). Missing required driver without exported proof is BLOCKED (driver: <name>). Use ticket/TC integrations only when configured; otherwise request exports or mark that lane BLOCKED.
- Capture applicable logs, screenshots, traces, or terminal summaries as <AC|step>-<before|after>.* under .playwright-cli/<session>/ or .appium-mcp/<session>/.
- For bug fixes, prove before-failure and after-success; preserve every applicable driver and verification lane.
PASS only when all approved criteria are proven and required approval/independent review gates are met; FAIL when a defect or missed requirement remains; BLOCKED when environment, credentials, or approval prevents proof. Feature verified status confirms technical delivery against contract; separate delivery proof from observed business success (delivery != causal ROI).
If observed behavior exceeds the approved low-risk brief, do not silently change scope or redefine criteria: route the decision to the owner, then verify against the resolved contract. Governed behavior drift requires PRD/SRS updates before PASS.
Record low-risk checks, outcomes, and evidence in chat/task report; do not require new BRD/PRD/SRS, task-list, REQ/AC-ID, trace, or walkthrough artifacts. Governed work updates BRD-to-PRD-to-SRS/FRS trace and docs/srs/srs-walkthrough-[slug].md. When initiative uses product evidence (docs/product/<slug>/evidence.json), carry measurement owner, registered MET baseline OR exact scoped exception DEC, query, instrumentation, cohort, window, guardrails, and review trigger; never fabricate agent-created baselines, approvals, or ROI. Proposal in ledger is not host execution or deployment permission.

Read the full file on GitHub · 83 lines

Changes

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.

12d ago Changed · -1 lines 82d89d0e4012
20d ago Changed · -14 lines 8af21ed2b797
28d ago Changed · +1 lines 82d99b21e85b
1mo ago Changed · -2 lines 31109f288243
1mo ago Changed d341d991a67a
1mo ago First seen · 99 lines · 23 tokens per session scan A c0983bbe3794

Subscribe to this mod's changes

verify-work is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 1,102 once invoked, about $0.0001 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-09-03.

E2E testing React Testing Unit testing best-practices coding-standards flutter nestjs nextjs

verify-work

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Verify Work Skill

Instructions

Verify Work Workflow

What this file has done since we first saw it

Other skills, from other repositories

testing-guide

verify

testing

browser-automation

vue-idioms

python-idioms