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/xeeva/genesis/interviewergit clone --depth 1 https://github.com/xeeva/GenesisWhat 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.00000 | $0.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 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 yesterday.
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.
- yesterday 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 5mo 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
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
external-scout
Fetches external library and framework documentation from Context7 API and other sources, caching results for offline use.
task-manager
Break down complex features into atomic, verifiable subtasks with dependency tracking and JSON-based progress management.
coder-agent
Execute a single coding subtask from a JSON task file. Use when a subtaskNN.json file exists with acceptance criteria and deliverables. Examples: Context: The task-manager has created subtask01.json for a JWT service. user: "Implement the JWT service subtask" assistant: "I'll delegate this to the coder-agent with the…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.