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 skills/husniadil/ekstend/interviewnpx skills add husniadil/ekstend --skill interviewgit clone --depth 1 https://github.com/husniadil/ekstendWrote 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/husniadil/ekstend/interview)<a href="https://agentmods.dev/skills/husniadil/ekstend/interview"><img src="https://agentmods.dev/badge/skills/husniadil/ekstend/interview.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.00023 | $0.05716 |
| Opus 5 | $0.00012 | $0.02858 |
| Sonnet 5 | $0.00005 | $0.01143 |
| Haiku 4.5 | $0.00002 | $0.00572 |
Grade A, and why
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 4d 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 — 844 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview
A deep requirements gathering skill that uncovers hidden requirements, edge cases, and trade-offs through thoughtful, in-depth questioning.
Core Philosophy
Interviewer, Not Order Taker
Don't just accept the initial request at face value. Your role is to:
- Uncover requirements the user hasn't explicitly considered
- Surface edge cases and failure modes before they become bugs
- Clarify trade-offs so the user makes informed decisions
- Ensure the implementation plan will actually solve the real problem
Bad pattern: User says "add login", you start implementing login Good pattern: User says "add login", you ask about session management, OAuth vs password, account recovery, rate limiting, existing auth systems, mobile app integration...
Workflow: CDEEPER
Follow this 7-phase interview workflow:
Phase 0: CONTEXTUALIZE (Codebase Exploration)
BEFORE asking any questions, explore the codebase to understand existing patterns:
- Identify the tech stack: Use Glob/Grep to find package.json, requirements.txt, go.mod, etc.
- Find related code: Search for similar features or patterns already implemented
- Understand conventions: Look at existing code style, naming, architecture patterns
- Check integrations: Identify databases, APIs, services already in use
This prevents asking obvious questions like "what database should we use?" when PostgreSQL is already used everywhere.
# Example exploration
Glob: **/package.json, **/requirements.txt
Grep: "database", "prisma", "sequelize", "mongoose"
Read: src/config/, src/lib/
Skip questions about things you can infer from the codebase. Only ask when there's genuine ambiguity or the new feature requires a different approach than existing patterns.
Phase 1: DISCOVER
Understand the core intent before asking questions.
Input Handling:
- Prompt only: Analyze the request directly
- Plan file path provided: Read the file using Read tool
- Both provided: Plan file takes precedence; prompt provides additional context
- File not found: Inform user and ask them to provide the correct path or describe requirements directly
What ships with it
1 file 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.
- 4d ago First seen · 844 lines · 23 tokens per session scan A f4083aa6be1b
interview is a skill published in the GitHub repository husniadil/ekstend (1 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 5,716 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
subagent-driven-development
Use when a written implementation plan exists and the user wants to execute it — "execute this plan", "implement the plan", "run the plan", "build it", "subagent-driven development". Plans + confirms in this session, then hands a lightweight task list to a deterministic background Workflow that runs per-task implement…
brainstorming
Use before feature or design work that carries real ambiguity or a load-bearing decision, ahead of writing implementation code — explores intent, requirements and design first. Do NOT use for trivial changes, mechanical edits, or work whose design is already settled.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Do NOT use once the cause is already established, or for adding new behaviour — that is implementation, not diagnosis.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Do NOT use inside the subagent-driven-development loop, which runs its own per-task implement→review→fix cycle and supersedes this skill there.
adr
Use when the user knows what they want built and says "/adr", "write an ADR for X", "decide and build X", or "ADR-driven". Turns an intent into a grounded, cited, build-ready ADR at docs/adr/YYYY-MM-DD- .md — load-bearing decisions surfaced to the human — then hands off to the subagent-driven-development loop. For…
frontend-design
Guidance for distinctive, intentional frontend/UI design — aesthetic direction, typography, layout, motion, and copy — when building new UI or reshaping existing UI. Gates by scope before designing: a light/surgical change (one component, one page section, extending an existing design system) gets inline design…