A guided user acceptance testing session that presents a verified feature in plain language and records whether a business approver accepts it. UAT is a final check by the people who will use or own the result.

Use it to map acceptance criteria to observable outcomes, run a business-facing demo, and capture approval or rejection.

It turns technical test results into a clear business decision about whether the feature is acceptable for release.

uat-signoff — 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 uat-signoff

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/uat-signoff/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/uat-signoff)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/uat-signoff"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/uat-signoff/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/uat-signoff"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/uat-signoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 838 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 warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 46
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

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.00027	$0.00838
Opus 5.5	$0.00011	$0.00335
Sonnet 5.5	$0.00005	$0.00168
Haiku 4.5	$0.00003	$0.00084

Measured today against content hash 750afa39cef8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

uat-signoff 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 today.

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/uat-signoff/SKILL.md · 81 lines

How it starts

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

Uat Signoff Skill

[!IMPORTANT] Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Instructions

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

UAT Signoff Workflow

Goal: Convert a verify-work PASS into an explicit, evidence-linked business acceptance decision before release.

Steps

Load scope:
- verify-work report, AC list, PRD/BRD-lite business objective, open defect ledger, residual risks, and inherited operator_profile per skills/quality-engineering/quality-engineering-test-plan-authoring/references/lifecycle-and-roles.md.
- Load common-operator-profile; release_confidence from test-loop/quality-engineering-automation-health.
Draft demo script (V-Model Level 1 Acceptance):
- Map each AC to an observable business outcome in plain language; technical details and residual risks go to appendix.
- For operator_profile=business or hybrid, this plain-language script is the primary artifact.
Walk the signoff:
- Present each AC outcome, open defects, and residual risks (e.g. untested device cells, waived non-blockers).
- Technical PASS confirms contract verification only; human approver accepts or rejects business delivery.
- Ask max 3 blocking questions at a time with a recommended default and 2-3 options.
Capture decision:
- Signoff owner, date, per-AC accept/reject, and accepted residual risks. Reject on any AC -> route to dev-fix.
- Full accept -> route to deploy-release.
Persist:
- Write the run record to artifacts/runs/[slug]/[compactISO]-uat-signoff.json when file writes are allowed.

Runtime Contract

Use after verify-work PASS on a feature, before deploy-release.
Required inputs: a PASS verification report with an AC list to demo against.
Return BLOCKED only when no verification report exists or the approver is unavailable in autonomous/channel mode.

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

today Changed · -2 lines 750afa39cef8
28d ago Changed · +1 lines 582405f282bd
1mo ago Changed 92c8fe1282a3
1mo ago Changed · +1 lines 272af85ac814
1mo ago First seen · 81 lines · 27 tokens per session scan A 829ff9e4b5ca

Subscribe to this mod's changes

uat-signoff is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 838 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 best-practices coding-standards flutter nestjs nextjs

uat-signoff

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

Uat Signoff Skill

Instructions

UAT Signoff Workflow

Steps

Runtime Contract

What this file has done since we first saw it

Other skills, from other repositories

verify

browser-automation

mobile-testing

test-e2e

test-integration

testing-guide