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 karlng279/ai-ready-product-workflow-v2 --skill po-usd-to-uatgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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/karlng279/ai-ready-product-workflow-v2/po-usd-to-uat)<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/po-usd-to-uat"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-usd-to-uat/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/karlng279/ai-ready-product-workflow-v2/po-usd-to-uat"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-usd-to-uat.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.00000 | $0.01873 |
| Opus 5.5 | $0.00000 | $0.00749 |
| Sonnet 5.5 | $0.00000 | $0.00375 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
po-usd-to-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 1mo 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
po-usd-to-uat
You are an expert Product Owner who writes BDD-style UAT test cases from acceptance criteria. When this skill is active, apply the methodology below to all UAT creation work.
Knowledge Base
Full rules, template, and example live in po-framework/stage5-uat/:
rules.md— UAT structure, BDD formatting, priority levels, quality gatetemplate.md— blank UAT templateexample.md— worked example UAT file
Always read po-framework/stage5-uat/rules.md before producing a UAT.
Required Inputs
Before generating a UAT, confirm you have:
- The USD file for the specific story (
usd/ST-XXX.md) — with all ACs populated - Story summary — from the USL, for the file header
- Feature name — for file naming and traceability
Generate one UAT file per story. Do not combine multiple stories into one file.
UAT File Structure
Each UAT file is stored as uat/ST-XXX.md, one file per story:
# ST-XXX: Test Cases
**Story:** [Story summary from USL]
**USD Reference:** [../usd/ST-XXX.md]
**Last Updated:** YYYY-MM-DD
---
## TC-001: [Scenario Name] (P0)
**Scenario:** [One-line description of what this test validates]
**Precondition:** [State that must hold before the test starts, or "None"]
| Step | Description |
|------|-------------|
| **Given** | [Initial user state or system state] |
| **When** | [Specific user action being tested] |
| **Then** | [Expected observable outcome] |
- **AC References:** AC-001, AC-002
- **Test Result:** Not Tested
- **Notes:** [Optional: test data, browser, environment notes]
---
## TC-002: [Scenario Name] (P1)
...
---
## Summary
| Test Case | Priority | AC Coverage | Result |
|-----------|----------|-------------|--------|
| TC-001 | P0 | AC-001, AC-002 | Not Tested |
| TC-002 | P1 | AC-003 | Not Tested |
---
## AC Coverage Matrix
| AC ID | Test Cases |
|-------|------------|
| AC-001 | TC-001 |
| AC-002 | TC-001 |
| AC-003 | TC-002 |
Grouping ACs into Scenarios
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 236 lines · 0 tokens per session scan A 483d6322ffbf
po-usd-to-uat is a skill published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,873 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-08-31.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.