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/elevanaltd/hestai-mcp/agent-interviewnpx skills add elevanaltd/HestAI-MCP --skill agent-interviewgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/agent-interview)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/agent-interview"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/agent-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.1 | $0.00000 | $0.01781 |
| Opus 5 | $0.00000 | $0.00890 |
| Sonnet 5 | $0.00000 | $0.00356 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
agent-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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===SKILL:AGENT_INTERVIEW=== META: TYPE::SKILL VERSION::"1.1.0" STATUS::ACTIVE PURPOSE::"Structured interview protocol for agent identity assessment. Extracts behavioral evidence for v8.1 agent file authoring with chassis-profile mapping."
§1::CORE MISSION::"Extract the behavioral truth of an agent's identity, authority, and operational modes through structured questioning" AUTHORITY::"Any agent loading this skill can conduct agent interviews" OUTPUT::"Structured assessment document suitable for agent-expert authoring pass"
§2::PROTOCOL INTERVIEW_SEQUENCE::[ // §1::IDENTITY questions Q01::"What is your primary role in one sentence?[validates::MISSION]", Q02::"What do you actually DO vs what your file says you do? Have you ever been invoked for real work in this system? If so, give an example. If not, say so.[validates::behavioral_fidelity]", Q03::"When should someone call you vs another agent? Give a concrete example.[validates::boundary_clarity]", Q04::"What can you BLOCK? What can you only advise on? Give examples.[validates::AUTHORITY]", // §2::OPERATIONAL_BEHAVIOR questions Q05::"Walk me through how you handle a typical task start to finish.[extracts::PROTOCOL]", Q06::"What should you NEVER do? Give a concrete example of when you almost did it.[validates::MUST_NEVER]", Q07a::"What EXACTLY do you receive as input — a PR diff, file contents, a structured assessment, a build plan? What format is it in, and which agent or source provides it?[extracts::HANDOFF_INPUT]", Q07b::"What EXACTLY do you produce as output — a verdict, a modified file, a structured report? What format must it be in, and which specific agent consumes it?[extracts::HANDOFF_OUTPUT]", Q07c::"What specific, measurable condition triggers escalation, and who specifically receives it? Not 'critical flaws' — give me a threshold and a named target. Example: 'more than 3 blocking P0 findings → critical-engineer'.[extracts::ESCALATION_TRIGGER⊕ESCALATION_TARGET]", // §3::CAPABILITIES questions Q08::"Which skills do you need EVERY time, regardless of context, and why?[maps::CHASSIS]", Q09::"Do you have distinct operational modes? What changes between them?[discovers::PROFILES]", Q10a::"For each skill and pattern listed in your file, check if it exists on disk. Report which are real and which are phantom.[detects::phantom_references]", Q10b::"For the skills that DO exist — do you actually use them? How? For those that don't — what would you use them for if they existed?[validates::capability_usage]", // §4::INTERACTION_RULES questions Q11::"What output format do you produce? Show me an example.[validates::GRAMMAR]", // Meta questions Q12::"What is missing from your current definition that you wish you had?[discovers::gaps]", Q13::"Is there overlap between you and another agent that should be resolved?[detects::boundary_conflicts]", // Cognition fit Q14::"Ignoring any cognition information in your agent file as it may be incorrect, review all cognition types (LOGOS, ETHOS, PATHOS) from library/cognitions/. Rank them in order of what you perceive to be most applicable to your role and explain why.[validates::COGNITION]", // Output completeness Q15::"What should your output look like when you PASS something vs when you BLOCK something? Show examples of both.[validates::GRAMMAR_COMPLETENESS]" ]
PRE_INTERVIEW::[ "If modifying an existing agent, read the agent's current .oct.md file", "Read all three cognition files from library/cognitions/", "Note current skills and patterns listed in §3::CAPABILITIES (if existing agent)", "Check which listed skills and patterns actually exist on disk (if existing agent)" ]
INTERVIEW_RULES::[ "Ask questions conversationally, not as a checklist", "Follow up on surprising or contradictory answers", "Note when stated behavior contradicts the agent file", "Record verbatim quotes that capture the agent's actual self-understanding", "End with: 'Is there anything about your identity I haven't asked about?'" ]
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.
- 5d ago First seen · 114 lines · 0 tokens per session scan A 78f4575c88b0
agent-interview is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,781 tokens. 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…