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 The-AI-Directory-Company/agents-and-skills --skill stakeholder-interviewgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/stakeholder-interview)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/stakeholder-interview"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/stakeholder-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/the-ai-directory-company/agents-and-skills/stakeholder-interview"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/stakeholder-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.00034 | $0.01637 |
| Opus 5 | $0.00017 | $0.00818 |
| Sonnet 5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
stakeholder-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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Interview Guide
Before you start
Gather the following from the user:
- Who is the stakeholder? (Name, role, department, decision-making authority)
- What is the project or initiative? (Brief context on what you are eliciting requirements for)
- What do you already know? (Existing documents, previous interviews, known constraints)
- What is the interview goal? (Discovery, validation, priority alignment, or constraint mapping)
If the user says "I just need to ask some questions," push back: "What decision will this interview inform? Start there — it shapes every question you ask."
Interview guide template
1. Preparation (before the interview)
- Review all available documentation: project briefs, prior meeting notes, org charts, and existing requirements.
- Identify the stakeholder's likely concerns based on their role — executives care about ROI and timelines, operators care about workflows and edge cases, end users care about pain points and usability.
- Draft 8-12 questions using the core question types below. Sequence them from broad to specific.
- Prepare a one-paragraph project summary to share at the opening — the stakeholder should not have to guess why they are there.
- Write down your top 3 assumptions about this stakeholder's perspective. You will test these during the interview.
2. Opening (first 5 minutes)
- Thank the stakeholder for their time. State the interview purpose in one sentence.
- Share the one-paragraph project summary. Ask: "Does this match your understanding, or would you frame it differently?"
- Set expectations: approximate duration, how their input will be used, and that there are no wrong answers.
- Ask permission to take notes or record.
3. Core questions by type
Choose 2-3 types per interview based on your goal. Do not try to cover all four in a single session.
Problem discovery
- "What is the biggest challenge your team faces with [process/system] today?"
- "Walk me through what happens when [problem scenario] occurs."
- "If you could fix one thing about how this works today, what would it be and why?"
What ships with it
3 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.
- 9d ago First seen · 142 lines · 34 tokens per session scan A 0220917a7f3d
stakeholder-interview is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,637 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
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.