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 cenconq25/claude-code-app-studio --skill user-test-reportgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/user-test-report)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/user-test-report"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/user-test-report/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/cenconq25/claude-code-app-studio/user-test-report"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/user-test-report.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01546 |
| Opus 5 | $0.00020 | $0.00773 |
| Sonnet 5 | $0.00008 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
user-test-report 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User-Test Report
The output of beta tests, usability sessions, and TestFlight / Play internal-testing waves. Two modes: produce a fresh report template a researcher fills in during the session, or take messy notes and turn them into a structured analysis.
Phase 1: Mode
Parse the argument:
--new— produce a blank report template for an upcoming session.--from=<path>— analyze raw notes at the given path.--session=<id>— locate session notes by ID underproduction/research/sessions/.
If no flag, ask the user which mode.
Phase 2: Read Project Context
Read in parallel:
CLAUDE.mdand.claude/docs/technical-preferences.md.- Active PRDs under
design/prd/. - Latest milestone in
production/milestones/. - Any prior session reports in
production/research/.
This context anchors findings back to PRD requirements and ongoing stories.
Phase 3A: New-Template Mode
Compose a template the researcher will fill in:
# User Test Report — [session-id]
**Date**: [date]
**Type**: [moderated remote | unmoderated remote | in-person | TestFlight | Play closed test]
**Build version**: [version + commit]
**Researcher**: [name]
**Participants**: [N]
## Goals
- [primary research question]
- [secondary]
## Recruitment
- Source: [pool]
- Demographics summary: [age, region, device class]
- Consent obtained: [yes — link to consent form]
## Tasks
| # | Task | Success criterion | Notes |
| 1 | Sign up | Reaches home screen in < 90s | |
| 2 | First paywall | Understands tiers; chooses or declines | |
| 3 | [feature] | [criterion] | |
## Per-Participant Results
| Participant | Task 1 | Task 2 | Task 3 | Notes |
## Observations (raw)
[Free text. Time-stamped if possible. One bullet per observation.]
## Quotes (direct)
- "[quote]" — Participant N
## Friction Map
| Screen | Friction | Severity | Frequency |
## Findings
### Confirmed (PRD assumptions verified)
- [finding] — confirms [PRD ref]
### Disconfirmed
- [finding] — challenges [PRD ref]
### New Insights
- [finding] — no PRD coverage; recommend [action]
## Recommendations
| Recommendation | Priority | Owner | Linked story / bug |
## Next Steps
- [action]
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 · 246 lines · 41 tokens per session scan A dca7e6b15507
user-test-report is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,546 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…