agentmods.dev

verify-work

verify-work is a command for Claude Code from HoangNguyen0403/agent-skills-standard. It costs 0 tokens per session (793 once invoked), scanned A, original, MIT.

A verification workflow that checks delivered feature, bug, interface, API, mobile, security, or deployment work against its acceptance criteria. Acceptance criteria are the specific conditions that must be true for work to be considered complete.

In plain words
What is it for?
Use it to run appropriate automated checks, inspect user-facing behavior, and collect logs, screenshots, or traces for handoff.
Why use it?
It replaces informal claims that something works with recorded checks and evidence. It can expose missing test coverage or an unverified delivery lane.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 565repo +4 3d ago A scan 0 tokens original MIT

Good fit Use it to run appropriate automated checks, inspect user-facing behavior, and collect logs, screenshots, or traces for handoff.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/verify-work
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
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.

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

Made for: Claude Code.

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.

agentmods badge for verify-work

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/verify-work/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/verify-work)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/verify-work"><img src="https://agentmods.dev/badge/commands/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.

agentmods 80×15 button for verify-work

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/verify-work"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/verify-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 793 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00793
Opus 5 $0.00000 $0.00396
Sonnet 5 $0.00000 $0.00159
Haiku 4.5 $0.00000 $0.00079

Measured 9d ago against content hash 3a9bc22f67bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 9d 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.

.claude/commands/verify-work.md · 90 lines

How it starts

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

Verify Work

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Input: $ARGUMENTS

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

Execute the following steps for $ARGUMENTS.

Verify Work Workflow

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

Steps

  1. Load scope:
    • BRD-lite, PRD, SRS/FRS, ticket, implementation plan, release note, acceptance criteria, non-goals, changed files, matched skills, and inherited operator_profile (carry, do not re-infer).
  2. Select verification lanes:
    • Unit/component, integration/API, E2E/visual, mobile, security, migration, or deployment smoke.
  3. Execute:
    • Run the smallest reliable automated checks first.
    • Use Playwright/Appium only when user-facing behavior changed.
    • Use Zephyr/Jira/GitHub/GitLab/ADO MCPs only when configured; otherwise record local evidence.
    • If external MCP is unavailable, ask for exported ticket/PR/TC data or mark that lane BLOCKED.
    • Capture Evidence: logs, screenshots, traces, or terminal output summaries.
    • Comparative Audit: If it's a bug fix, prove the "Before" (failure) vs "After" (success).
  4. Judge:
    • PASS: all acceptance criteria proven.
    • FAIL: original bug or missed requirement still reproducible.
    • BLOCKED: environment, credentials, or approval prevents proof.
  5. Record evidence:
    • If verification reveals behavior drift, require PRD/SRS updates before PASS.
    • Update traceability notes from BRD objective -> PRD requirement -> SRS/FRS contract -> verification evidence.
    • Update project-local docs/srs/srs-walkthrough.md.
    • Route next step back to implementation or dev-fix.

Runtime Contract

  • Use after implementation, before handoff, or when validating a bug fix.
  • Required inputs: explicit scope plus acceptance criteria or expected behavior.
  • Return BLOCKED only when environment, credentials, or approval prevents proof.

Read the full file on GitHub · 90 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.

  1. 9d ago First seen · 90 lines · 0 tokens per session scan A 3a9bc22f67bb

Subscribe to this mod's changes

verify-work is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 793 tokens. 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.

Project managementReactTestingbest-practicescoding-standardsflutternestjsnextjs
Related

Other commands, from other repositories

debug

Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.

first-fluke/fullstack-starter · 28 tokens

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 35 tokens

schedule

Register a scheduled agent job from a natural-language schedule request — parse the interval, resolve agent-id + prompt + workspace, call oma schedule:add, then confirm with oma schedule:list.

first-fluke/fullstack-starter · 35 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 19 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 20 tokens