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 agentmods add skills/tomsej/pi-ext/wf-uatnpx skills add tomsej/pi-ext --skill wf-uatgit clone --depth 1 https://github.com/tomsej/pi-extWrote 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/tomsej/pi-ext/wf-uat)<a href="https://agentmods.dev/skills/tomsej/pi-ext/wf-uat"><img src="https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-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.00076 | $0.00825 |
| Opus 5 | $0.00038 | $0.00413 |
| Sonnet 5 | $0.00015 | $0.00165 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
wf-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 6d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wf-uat — user acceptance testing
Argument: absolutní cesta ke kontraktu (mimo repo). Nikdy neměň kód, testy ani konfiguraci repa — vadu nahlas, opravy patří do implementace.
UAT NENÍ druhý běh gatů — gate už kritéria dokázal testy a jejich opakování (nebo šťouchání do interních API) vyrábí falešnou jistotu, ne novou informaci. Definice: pohled uživatele, jeho rozhraním, na běžící instanci — CLI jak by ho napsal, UI jak by klikal, API jak by volal.
Samostatná jednotka: pipeline ji volá jako poslední fázi, uživatel na ní iteruje sám. Vstup = cesta ke spec, výstup = český report.
Prostředí
- DISPOSABLE lokální instance, spuštěná obvyklým způsobem projektu (docker compose, dev server, seedovaná lokální DB) — nikdy sdílené ani produkční prostředí.
- Volný ne-default port — paralelně můžou běžet UAT jiných kontraktů.
- Scénáře měnící stav jsou v sandboxu v pořádku — „neměň" platí na repo, ne na data sandboxu.
- Všechno timeboxuj, instanci nakonec shoď, nenech běžet watch/dev server.
- Neumí-li projekt disposable instanci, napiš to — ty scénáře jdou do ručního seznamu.
Postup
- Přečti kontrakt: sekci UAT a všechna akceptační kritéria.
- Odvoď scénáře: každé kritérium ≥ 1 scénář, plus explicitní UAT položky. Jen uživatelský pohled (co vidí, píše, kam kliká). Scénář, který by jen zopakoval gate, přeskoč a označ jako pokrytý gatem.
- Co umíš, proveď sám proti disposable instanci. Webové UI přes
agent-browserCLI, je-li nainstalované; bez něj jdou UI scénáře do ručního seznamu — nikdy nepředstírej průchod. - Report CELÝ ČESKY (PR je anglicky, tenhle report je pro uživatele — záměrně):
- co bylo ověřeno automaticky (scénář → výsledek, přesné příkazy/kroky),
- co pokrývá gate a UAT to neopakuje (kritérium → test),
- Ruční kroky pro uživatele: číslovaný postup — kde kliknout, co spustit, co přesně čekat (jeden krok = jedno pozorovatelné chování),
- zbytková rizika / co UAT nepokrylo a proč.
- Report vytiskni (patří do finálního reportu dirigenta), nikdy ho neposílej jako komentář na PR. Každé kritérium se v něm musí objevit — nenamapované kritérium je nález, ne tiché přeskočení.
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.
- 6d ago First seen · 50 lines · 76 tokens per session scan A 1eb7e4e0dee7
wf-uat is a skill published in the GitHub repository tomsej/pi-ext (69 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 825 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…