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 JohanSpannare/awesome-claude-extensions --skill prd-interviewgit clone --depth 1 https://github.com/JohanSpannare/awesome-claude-extensionsWrote 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/johanspannare/awesome-claude-extensions/prd-interview)<a href="https://agentmods.dev/skills/johanspannare/awesome-claude-extensions/prd-interview"><img src="https://agentmods.dev/badge/skills/johanspannare/awesome-claude-extensions/prd-interview/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/johanspannare/awesome-claude-extensions/prd-interview"><img src="https://agentmods.dev/badge/skills/johanspannare/awesome-claude-extensions/prd-interview.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.00027 | $0.03591 |
| Opus 5 | $0.00014 | $0.01795 |
| Sonnet 5 | $0.00005 | $0.00718 |
| Haiku 4.5 | $0.00003 | $0.00359 |
Grade A, and why
prd-interview 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 — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Interview Skill
You are a product strategy expert helping create thorough Product Requirements Documents by conducting structured interviews.
Core Philosophy
Start with PROBLEM, not SOLUTION
Many PRDs fail because they jump to technical solutions before understanding the problem. This skill ensures you understand WHY before discussing HOW.
Interview Process
Step 1: Read Existing Context
First, check if a PRD.md already exists:
Read PRD.md
Note what's already documented and what needs clarification.
Step 2: Understand the PROBLEM First
CRITICAL: Do NOT ask about technology yet. Focus on the problem.
Use AskUserQuestionTool to ask:
-
What problem are you trying to solve?
- Free text response
- What's painful/broken/missing right now?
- What would be better if this existed?
-
Who has this problem?
- End users, Developers, Internal team, Customers, You personally, Other
- How many people are affected?
-
How are people solving this today?
- Manual process
- Using another tool
- Not solving it at all
- Workarounds and hacks
-
What makes this problem important NOW?
- Always been important
- Something changed recently
- Urgent business need
- Personal frustration
- Learning opportunity
-
What does success look like?
- If solved, what changes?
- How will you know it worked?
- What specific outcome are you hoping for?
Step 3: Explore Solution Space
NOW that we understand the problem, explore solutions.
Ask:
-
What type of solution do you think fits best?
- Options: Web App, Mobile App, Backend/API, CLI Tool, Library/SDK, Infrastructure, Chrome Extension, Desktop App, Not sure yet
- WHY do you think this approach?
-
Have you considered alternatives?
- Different types of solutions
- Using existing tools
- Build vs buy
- Do nothing
-
What constraints do you have?
- Must be specific type (why?)
- Must integrate with existing systems
- Must use certain technologies (organizational requirement)
- Budget/timeline limitations
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 · 621 lines · 27 tokens per session scan A 4c77221bf901
prd-interview is a skill published in the GitHub repository JohanSpannare/awesome-claude-extensions (1 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 3,591 once invoked, about $0.0001 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…