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 uat-signoffgit 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/uat-signoff)<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.
<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>- NVIDIA SkillSpector warn
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.
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.00686 |
| Opus 5 | $0.00014 | $0.00343 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
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 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 — 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.
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:
UAT Signoff Workflow
Goal: Convert a verify-work PASS into an explicit, evidence-linked business acceptance decision before release.
Steps
- Load scope:
verify-workreport, AC list, PRD/BRD-lite business objective, and inheritedoperator_profile(carry, do not re-infer).- Load
common-operator-profile.
- Draft demo script:
- Map each AC to an observable business outcome in plain language; omit file paths, commands, and code identifiers from the primary script.
- For
operator_profile=businessorhybrid, this plain-language script is the primary artifact; keep technical trace in a trailing appendix.
- Walk the signoff:
- Present each AC outcome and ask the approver to accept or reject.
- Ask max 3 blocking questions at a time with a recommended default and 2-3 options.
- Record conditions attached to any conditional acceptance.
- Capture decision:
- Signoff owner, date, and per-AC accept/reject status.
- Reject on any AC -> route to
dev-fix. - Full accept -> route to
deploy-release.
Runtime Contract
- Use after
verify-workPASS on a feature, beforedeploy-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.
Handoff Payload
slug,operator_profile, signoff owner, per-AC decision, conditions, outcome report, next workflow.
Blocking Questions
- Ask max 3 at a time with a recommended default and 2-3 options.
Output Template
# UAT Signoff: [Name]
## Demo Script (Plain Language)
## Per-AC Decision
| AC ID | Outcome Demonstrated | Decision | Conditions |
| --- | --- | --- | --- |
| [ac-id] | [outcome] | [accept/reject] | [conditions] |
## Signoff Owner And Date
## Technical Appendix
## Outcome Report
feature_status: implemented | partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: deploy-release | dev-fix
## Next Workflow
deploy-release | dev-fix
## Cost Report
Call `get_session_cost(workflow="uat-signoff")` before final handoff.
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 · 81 lines · 27 tokens per session scan A 829ff9e4b5ca
uat-signoff is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 686 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
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
flutter-mcp-cli-runtime-validation
Run Flutter MCP runtime validation from CLI in two steps (launch app, then run validate-runtime), including toolkit-extension gating, screenshot/layout capture, app error collection, optional reload verification, and retry handling for transient first-connect failures.