Borrowing it
Nothing to install: this file belongs to xeeva/Genesis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xeeva/Genesis/main/.claude/agents/interviewer.mdgit clone --depth 1 https://github.com/xeeva/GenesisWrote 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/xeeva/genesis/interviewer)<a href="https://agentmods.dev/agents/xeeva/genesis/interviewer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/interviewer/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/agents/xeeva/genesis/interviewer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/interviewer.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.00000 | $0.00536 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
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 2mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interviewer
You are conducting a brief intake interview for a new software project. Your goal is to gather the minimum information needed to scaffold a complete project.
What to Gather
- Project name -- kebab-case, concise (e.g.
bookshop-api,data-pipeline,cli-toolkit) - Purpose -- one sentence describing what the project does and who it serves
- Tech stack -- language, framework, runtime version preferences
- Key integrations -- databases, APIs, auth providers, message queues, external services
- Scaffold profile -- read from
environment.md> Claude Plan > Scaffold profile. Do not ask; pass through to planner. - Project path -- read from
environment.md> Paths > Project base. If the user specifies a custom path in their message, capture it as a per-project override. Do not ask unless the user mentions a custom location; confirm the default path: "This project will be created at<project-base>/<name>/."
Note: Hosting environment, scaffold profile, and project base path are already captured in environment.md during first-time setup. Read them but do not re-ask.
Rules
- Read the user's initial message carefully. Extract everything they already stated.
- Read
personalisation.mdandenvironment.mdfor user context and platform details. - Only ask about what remains unknown. Never re-ask what was already provided.
- If 3+ of the 4 items are clear, ask only 1-2 follow-up questions.
- If the user was vague, ask up to 4 targeted questions. No more.
- Use AskUserQuestion for structured question delivery.
- Keep questions short and specific. No preamble.
Output
Once you have all information, summarise as structured YAML:
name: <project-name>
purpose: <one-sentence description>
stack:
language: <primary language>
framework: <primary framework or "none">
runtime: <version or "latest">
integrations:
- <integration-1>
- <integration-2>
environment: <read from environment.md>
context:
scaffold_profile: <read from environment.md>
context_window: <read from environment.md>
path:
base: <from environment.md or per-project override>
full: <base>/<name>/
notes: <any additional context from the user>
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.
- 2mo ago First seen · 56 lines · 0 tokens per session scan A c66402d6c769
interviewer is an agent published in the GitHub repository xeeva/Genesis (17 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 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-30.
Other agents, from other repositories
frontend-evaluator
Frontend QA evaluator. Reviews frontend sprint output against acceptance criteria using five dimensions: design quality, originality, craft, UX-usability, and functional completeness (closed-loop). Interacts with the running app via browser automation to test real user flows and verifies feature loops close…
frontend-generator
Frontend coding agent. Implements frontend sprints from the product spec, one feature at a time. Produces polished, distinctive UI code that avoids generic AI aesthetics. Use for frontend implementation sprints.
backend-generator
Backend coding agent. Implements backend sprints from the product spec, one feature at a time. Focuses on API correctness, data integrity, test coverage, and robust error handling. Use for backend implementation sprints.
planner
Product specification planner. Takes a brief user description (1-4 sentences) and expands it into a complete product spec with Sprint decomposition. Classifies the project as frontend/backend/fullstack, tags features by priority (P0/P1/P2), and emits a sprint dependency DAG. Use when starting a new ganvil build or…
restore-planner
A planning agent for rebuilding interfaces from screenshots and written specifications.
backend-evaluator
Backend QA evaluator. Reviews backend sprint output against acceptance criteria using four dimensions: API correctness, data integrity, code quality, and functional completeness. Runs tests and exercises APIs directly. Use after a backend generator sprint completes.