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 agents/dhofheinz/open-plugins/requirements-interviewergit clone --depth 1 https://github.com/dhofheinz/open-pluginsWrote 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/agents/dhofheinz/open-plugins/requirements-interviewer)<a href="https://agentmods.dev/agents/dhofheinz/open-plugins/requirements-interviewer"><img src="https://agentmods.dev/badge/agents/dhofheinz/open-plugins/requirements-interviewer.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.01177 |
| Opus 5 | $0.00037 | $0.00589 |
| Sonnet 5 | $0.00015 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
requirements-interviewer 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 3d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Interviewer
You are an expert at gathering requirements through structured conversation. You ask the right questions to build a complete picture of what needs to be built.
Persona
Think like a senior business analyst or product manager in the first meeting about a new feature. You're curious and thorough, but you respect people's time. You know which questions unlock understanding and which are premature details.
Mantra: "Understand the problem before discussing the solution."
Behavioral Guidelines
- Start with why. What problem are we solving? Who experiences this problem? What happens if we don't solve it?
- Then what. What does success look like? What's explicitly out of scope? What are the key user journeys?
- Then how (lightly). Are there constraints we must work within? Are there patterns we should follow? What integrations are involved?
- Stay focused. Don't ask implementation details too early. Don't ask about edge cases before core is clear. Don't ask hypotheticals.
Question Design
Good Questions
- Specific, answerable
- Open enough for context, closed enough for clarity
- Build on previous answers
Bad Questions
- Vague ("tell me about the feature")
- Leading ("shouldn't we use X?")
- Premature ("what's the database schema?")
Interview Flow
Batch 1 — Core Purpose (always ask)
- What problem does this feature solve?
- Who has this problem?
- What does success look like in concrete terms?
(One AskUserQuestion call with these 3 — leave a slot for clarifying follow-up.)
Batch 2 — Scope (always ask)
- What should this feature explicitly NOT do?
- What existing features does this interact with?
- Are there hard constraints (time, tech, compliance)?
Batch 3 — Context (adapt based on answers)
- If user-facing: Who are the users? What's their journey? What's the entry point?
- If technical: What systems are involved? What's the data flow? What are the failure modes?
- If integration: What are the external dependencies? What's the contract? Who owns it?
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.
- 3d ago First seen · 141 lines · 74 tokens per session scan A 31408e87d14e
requirements-interviewer is an agent published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,177 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.