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/paralleldrive/aidd/aidd-user-testingnpx skills add paralleldrive/aidd --skill aidd-user-testinggit clone --depth 1 https://github.com/paralleldrive/aiddWhat 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.00033 | $0.00992 |
| Opus 5 | $0.00016 | $0.00496 |
| Sonnet 5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
aidd-user-testing 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Testing Generator
Use UserJourney and Persona from /aidd-product-manager
Generate dual test scripts: human (think-aloud protocol, video recorded) + AI agent (executable with screenshots).
Types
UserTestPersona { ...Persona role techLevel: "novice" | "intermediate" | "expert" patience: 1..10 goals: string[] }
UserTestStep { ...Step action intent success checkpoint?: boolean }
Scripts
HumanScript:template { """
Test: ${journey.name}
Persona: ${persona.name} — ${persona.role}
Pre-test
- Start screen recording
- Clear state (cookies, cache, cart)
- Prepare credentials if needed
Instructions
Read each step out loud before attempting it. Think aloud as you work - this helps reviewers follow along.
Steps
For each step:
- Goal: ${step.intent}
- Do: ${step.action}
- Think aloud: What do you see? Any friction?
- Success: ${step.success}
Post-test
- Stop recording
- What was confusing?
- What worked well?
- Would you complete this in real life? """ }
AgentScript:template { """
Agent Test: ${journey.name}
Environment: Drive real browser, discover UI by looking (no source code access)
Persona behavior:
- Patience: ${persona.patience}/10
- Retry: ${persona.techLevel == "expert" ? "immediate" : "exponential backoff"}
- On failure: ${persona.patience > 5 ? "retry" : "abort"}
Execution
For each step, narrate your thoughts like a human tester:
- Interact with real UI: ${step.action}
- Express confusion, expectations, what you see
- Validate rendered result: ${step.success}
- Screenshot browser viewport if checkpoint or failure
- Record: difficulty (easy/moderate/difficult), duration, what was unclear
- Retry with backoff if failed and patient
Output Format
# Test Report: ${journey.name}
**Completed**: X of Y steps
## Step: [step name]
- **Status**: ✓ Success / ✗ Failed
- **Duration**: Xs
- **Difficulty**: easy/moderate/difficult
- **Thoughts**: [What I saw, expected, any confusion]
- **Screenshot**: [path if captured]
## Blockers
- [Any steps that couldn't be completed and why]
""" }
What ships with it
2 files 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.
- 2d ago First seen · 149 lines · 33 tokens per session scan A 4135d9a603cb
aidd-user-testing is a skill published in the GitHub repository paralleldrive/aidd (380 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 992 once invoked, about $0.0002 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
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
browser-recording
Record a browser flow as a video/GIF for evidence — animations, transitions, and multi-step interactions that a still screenshot cannot prove. Drives the project's own Playwright through a bundled runner, then converts to mp4 + GIF via ffmpeg. Use when the user asks to record a demo, capture a GIF or video of the UI…
web-browse
Open a REAL external web page so the user can see it in Kiro Crew's Browser panel. PRIMARY path is the browser MCP tool (drives the built-in native panel); playwright-cli is the fallback for remote/plain-browser sessions and for attached logged-in browsers. Use when the user wants to VIEW / verify / "show me" an…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…