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/lftpadilla/agent-dev-kit/live-qanpx skills add LFTPadilla/agent-dev-kit --skill live-qagit clone --depth 1 https://github.com/LFTPadilla/agent-dev-kitWhat 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 | $0.00077 | $0.00808 |
| Opus 5 | $0.00039 | $0.00404 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
live-qa 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-qa — drive the real app like a user
Use the Playwright MCP tools (mcp__playwright__browser_*) to walk a real
browser through a flow described in plain language, behaving like a user and
adapting to what's actually on screen. This catches what fixed specs can't:
broken states, dead ends, ugly errors, slow steps, console/network failures.
This is the exploratory/real-user layer. It does NOT replace committed
Playwright regression specs — pair the two (see playwright-stability).
Procedure
- Confirm target + flow. Ask for the URL (or local port) and the user journey to exercise (e.g. "sign up → connect an account → start onboarding"). Ask for test credentials if the flow needs auth.
- Navigate and snapshot.
browser_navigate, thenbrowser_snapshotto read the accessibility tree (prefer it over screenshots for deciding what to click — it's the structured truth). Screenshot (browser_take_screenshot) only to show the user a visual or capture a defect. - Act like a user, one step at a time.
browser_click/browser_type/browser_fill_form/browser_select_option. After each action, snapshot and verify the expected state appeared before moving on — no blind sequences. - Watch the plumbing. After key steps, pull
browser_console_messagesandbrowser_network_requests— flag JS errors, 4xx/5xx, slow calls, failed requests even when the UI "looks fine". - Probe like a real user, not a script. Try the empty state, the back button mid-flow, a double-click, an invalid input, a refresh after a mutation.
- Report. Per issue: where (step + URL), what happened vs expected, evidence (console/network/screenshot), severity. End with a short "flows that worked cleanly" list so the pass is legible.
Escalation — remote session browser (optional)
Playwright MCP is the default and covers almost everything. Escalate only when the flow needs a persistent, headful, human-watchable browser: a login/profile that must survive across runs, a site that blocks a fresh automated browser, or a step a human must finish (captcha, OTP, payment).
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.
- 2d ago First seen · 57 lines · 77 tokens per session scan A aa6df773b3fd
live-qa is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 808 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-31.
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…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
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.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.