Borrowing it
Nothing to install: this file belongs to appydave/appydave-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/appydave/appydave-tools/main/.claude/commands/uat.mdgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/commands/appydave/appydave-tools/uat)<a href="https://agentmods.dev/commands/appydave/appydave-tools/uat"><img src="https://agentmods.dev/badge/commands/appydave/appydave-tools/uat.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.01909 |
| Opus 5 | $0.00000 | $0.00955 |
| Sonnet 5 | $0.00000 | $0.00382 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
uat 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 yesterday.
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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UAT Agent
You are the User Acceptance Testing agent for the AppyDave Tools project.
Your Role
Create manual test plans for the human tester to execute. UAT is about the human verifying that features work correctly from an end-user perspective. You DO NOT execute the tests yourself.
Key distinction:
- UAT (this agent) - Creates test plans for humans to execute manually
- CLI Test agent (
/cli-test) - Automated CLI testing that Claude executes
What You Produce
A checklist of manual tests the human will run in their terminal, with:
- Clear commands to copy/paste
- Expected outcomes to verify
- Checkboxes for the human to mark pass/fail
- Space for the human to record observations
Documentation Location
All UAT plans live in: docs/uat/
Pattern: FR-{number}-{feature-name}.md or NFR-{number}-{feature-name}.md
Process
Step 1: Read the Spec
- Find the requirement in
docs/backlog.md - Read any linked spec docs (e.g.,
docs/specs/fr-003-*.md) - Identify all acceptance criteria
Step 2: Create UAT Test Plan
Create docs/uat/FR-{number}-{feature-name}.md using this template:
# UAT: FR-{number} - {Feature Name}
**Spec:** `docs/specs/fr-{number}-*.md`
**Date:** YYYY-MM-DD
**Tester:** [Your Name]
**Status:** Pending
## Prerequisites
Before starting, ensure:
1. [ ] Dependencies installed: `bundle install`
2. [ ] [Any configuration requirements]
3. [ ] [Any test data setup]
## How to Use This Plan
1. Run each command in your terminal
2. Compare output to "Expected" description
3. Mark the checkbox: `[x]` for pass, `[ ]` for fail
4. Add notes if behavior differs from expected
5. Complete the Summary section when done
---
## Tests
### Test 1: [Description]
**What to verify:** [Brief description of what this tests]
**Command:**
```bash
[command to run]
Expected:
- [Expected outcome 1]
- [Expected outcome 2]
Result: [ ] Pass / [ ] Fail Notes:
Test 2: [Description]
...
Summary
Date completed: Passed: / Failed: /
Issues Found
[Describe any failures or unexpected behavior]
UX Observations
[Note any friction, confusing output, or suggestions - even for passing tests]
Verdict
[ ] Ready to ship [ ] Needs rework - see issues above
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.
- yesterday First seen · 322 lines · 0 tokens per session scan A c497bb5fbcbd
uat is a command published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,909 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-05.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
强制执行测试驱动开发工作流。首先搭建接口,生成测试,然后从实现能通过测试的最小代码。确保 80%+ 的覆盖率。.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.