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/drvoss/everything-copilot-cli/interview-menpx skills add drvoss/everything-copilot-cli --skill interview-megit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/interview-me)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/interview-me"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/interview-me.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.00076 | $0.01338 |
| Opus 5 | $0.00038 | $0.00669 |
| Sonnet 5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
interview-me 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Me
Interview Me is for intent discovery before work starts. It is the step before a spec, plan, or implementation, when the user's first ask may still be a proxy for the real goal.
Unlike grill-me, which stress-tests an existing plan through dialogue, Interview Me is for
gathering missing intent from the requester and can produce a questionnaire-style batch when
interactive back-and-forth would be too slow.
When to Use
- The request is missing who, why, success criteria, constraints, or non-goals
- The user asked for a conventional artifact ("build a dashboard", "make it faster") without saying what problem that artifact solves
- You notice yourself filling in assumptions before any plan exists
- The user explicitly asks to be interviewed, challenged, or stress-tested before starting
When NOT to Use
| Instead of interview-me | Use |
|---|---|
| The request is already clear and self-contained | do the task |
| The user's intent is already clear, but an existing plan or spec now needs its assumptions pressure-tested | grill-me |
| The work is really about choosing Copilot mode, tools, or delegation path rather than discovering the user's desired outcome | task-intake-router |
| The user asked a factual or explanatory question | answer directly |
Loading Constraint
This skill needs an answerable user, but not always a live turn-by-turn exchange. If interactive back-and-forth is impractical, convert only the mutually independent unresolved questions into a questionnaire the requester can answer asynchronously. Do not invoke it when there is no responsible person who can answer.
Workflow
1. State your hypothesis and confidence
Before asking anything, write down:
- your best current read of what the user wants
- a confidence number from 0 to 100
If the number feels high but you cannot predict the next few answers, the number is too high.
2. Default to linear questioning; batch only independent clarifications
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 · 172 lines · 76 tokens per session scan A 04e3bfd2bc78
interview-me is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 76 tokens to every session and 1,338 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
keep-alive
Prevent computer sleep and continue working autonomously. Use when you need to step away but want work to continue.
hud
Configure HUD display options (layout, presets, display elements).
ralph
Self-referential loop until task completion with configurable verification reviewer.
configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language.
execute
Carry an approved task through to working, verified code.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…