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 uthumany/uthy-legacy-os --skill customer-interviewsgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/customer-interviews)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/customer-interviews"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/customer-interviews/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/uthumany/uthy-legacy-os/customer-interviews"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/customer-interviews.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.00030 | $0.01102 |
| Opus 5 | $0.00015 | $0.00551 |
| Sonnet 5 | $0.00006 | $0.00220 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
customer-interviews 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Discovery Interviews
Overview
Customer discovery interviews are the bedrock of evidence-based product management. This skill turns casual user conversations into structured discovery — helping you uncover real problems, avoid solution bias, and build products people actually need. Rooted in The Mom Test by Rob Fitzpatrick and Continuous Discovery Habits by Teresa Torres.
When to Use
- You're entering a new problem space with unvalidated assumptions
- You need to understand why users behave a certain way
- You want to test an opportunity before exploring solutions
- You're preparing for a product discovery sprint
- Don't use for: usability testing (use validation-interview instead), market research surveys (too structured), or customer satisfaction calls
Instructions
Phase 1: Plan the Interviews
- Define your learning goals — What 3-5 things do you want to learn? Frame as open-ended questions about past behavior, not future intent.
- Write the interview guide — Start with broad context, narrow to specifics. Never ask "Would you use X?" — ask "Tell me about the last time you dealt with Y."
- Recruit participants — Aim for 5-8 per segment. Use customer discovery criteria: they should have the problem, not necessarily use your product.
- Avoid bias — Do not mention your solution idea. Do not pitch. Do not lead.
Phase 2: Conduct the Interview
- Build rapport — Thank them, explain the goal is to learn, not sell. Ask permission to record.
- Ask about specific moments — "Walk me through the last time you..." beats "How often do you..."
- Listen for emotion — Strong frustration, workarounds, and surprising effort signal real problems.
- Use the Mom Test principles:
- Talk about their life, not your idea
- Ask about specifics from the past, not hypotheticals about the future
- Listen for commitments (time, introductions, money) — compliments are cheap
- Dig deeper — When they mention something interesting: "Tell me more about that." "Why did you do it that way?" "What happened next?"
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.
- 10d ago First seen · 104 lines · 30 tokens per session scan A 60f05101cc91
customer-interviews is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,102 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-31.
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…