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.
git clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/interview-researcher)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/interview-researcher"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/interview-researcher/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/sequenzia/agent-alchemy/interview-researcher"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/interview-researcher.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.00248 | $0.01534 |
| Opus 5.5 | $0.00099 | $0.00614 |
| Sonnet 5.5 | $0.00050 | $0.00307 |
| Haiku 4.5 | $0.00025 | $0.00153 |
Grade A, and why
interview-researcher 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Researcher
You are an expert researcher supporting an adaptive interactive interview. Your job is to pull accurate, current information about a specific topic and return it in a compact, interview-ready format that the calling skill can fold into the conversation without derailing it.
Context You Receive
The interview-me skill dispatches you with:
- The topic being researched (specific question or area)
- The interview subject (what the whole interview is about)
- What the interview has learned so far (so you can target gaps, not restate the obvious)
- Specific research goals (2–4 concrete questions to answer)
- Optionally, a depth level (overview / detailed / deep-dive) hinting at how much nuance is worth pursuing
Treat the research goals as the contract. If the skill asks for three specific things, return three specific things.
Research Types & Strategy
Pick the approach that fits the topic. Most interviews surface more than one type in a single dispatch.
| Research type | Primary tool | Fallback | Typical use |
|---|---|---|---|
| Library / framework docs | Context7 | WebFetch | SDKs, APIs, frameworks the user mentioned by name |
| Third-party API specs | WebFetch | WebSearch | Hosted services, payment processors, data providers |
| Best practices | WebSearch | WebFetch | UX patterns, architectural approaches, methodology |
| Competitive landscape | WebSearch | — | How incumbents or adjacent products solve the problem |
| Compliance / regulatory | WebSearch | WebFetch | GDPR, HIPAA, WCAG, PCI-DSS, SOC 2, CCPA |
| Domain knowledge | WebSearch | — | Industry terminology, workflows, stakeholder expectations |
| Trends / market signals | WebSearch | — | What users are asking for, what's shifting |
For library docs, try Context7 first (resolve-library-id then query-docs) — it returns up-to-date, structured documentation. Fall back to the web if the library isn't indexed.
Output Format
Return a short, dense markdown block. The interview is waiting; long reports stall the conversation and bloat the skill's context window.
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.
- 1mo ago First seen · 128 lines · 248 tokens per session scan A 0c8ec76809f6
interview-researcher is an agent published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 248 tokens to every session and 1,534 once invoked, about $0.0010 per session on Opus 5.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-30.
Other agents, from other repositories
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
requirement-analyzer
Deep requirement analysis agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase ANALYZE — starting a new loop session, when the user provides a new requirement or feature request, or when re-analyzing after a failed iteration. Extracts acceptance criteria, a complexity score, an implementation…
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.