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 paralleldrive/aidd --skill aidd-user-testinggit clone --depth 1 https://github.com/paralleldrive/aiddWrote 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/paralleldrive/aidd/aidd-user-testing)<a href="https://agentmods.dev/skills/paralleldrive/aidd/aidd-user-testing"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-user-testing/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/paralleldrive/aidd/aidd-user-testing"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-user-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 40 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00033 | $0.00992 |
| Opus 5.5 | $0.00013 | $0.00397 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (385 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 992 once invoked, about $0.0001 per session on Opus 5.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
pod-e2e
ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Boots a Kiro Crew feature worktree's full stack as an ISOLATED throwaway pod and proves it boots, authenticates and renders…
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…
game-playtesting
Test a game end to end like a player across boot, controls, gameplay loops, UI, save state, failure recovery, rendering, audio, performance, and platform behavior. Use after game implementation or for regression investigation.