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 HoangNguyen0403/agent-skills-standard --skill verify-workgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/verify-work)<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.
<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>- NVIDIA SkillSpector pass
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.00841 |
| Opus 5 | $0.00012 | $0.00420 |
| Sonnet 5 | $0.00005 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
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.
How it starts
The opening of the file, as written. The whole thing — 99 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.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
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.
Steps
- 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).
- BRD-lite, PRD, SRS/FRS, ticket, implementation plan, release note, acceptance criteria, non-goals, changed files, matched skills, and inherited
- Select verification lanes:
- Unit/component, integration/API, E2E/visual, mobile, security, migration, or deployment smoke.
- 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).
- Judge:
- PASS: all acceptance criteria proven.
- FAIL: original bug or missed requirement still reproducible.
- BLOCKED: environment, credentials, or approval prevents proof.
- 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.
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.
- 9d ago First seen · 99 lines · 23 tokens per session scan A c0983bbe3794
verify-work is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 841 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-09-03.
Other skills, from other repositories
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
testing
Skill "testing" from udecode/plate-playground-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
testing-strategies
Systematic testing for confidence without over-testing — the right test at the right level.