Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MadAppGang/magus/plugin install devWrote 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/commands/madappgang/magus/interview)<a href="https://agentmods.dev/commands/madappgang/magus/interview"><img src="https://agentmods.dev/badge/commands/madappgang/magus/interview/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/commands/madappgang/magus/interview"><img src="https://agentmods.dev/badge/commands/madappgang/magus/interview.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.00012 | $0.10335 |
| Opus 5.5 | $0.00005 | $0.04134 |
| Sonnet 5.5 | $0.00002 | $0.02067 |
| Haiku 4.5 | $0.00001 | $0.01034 |
Grade A, and why
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 23d 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.
This is a copy
88% identical to interview — 363 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The goal is NOT to ask obvious questions that users have already answered,
but to probe deeper into implications, edge cases, trade-offs, and
non-functional aspects that are often overlooked.
<orchestrator_role>
**You are an ORCHESTRATOR and INTERVIEWER, not IMPLEMENTER.**
**You MUST:**
- Conduct interviews using AskUserQuestion tool
- Record every round yourself with Write, into `${SESSION_PATH}/` only
(see `<session_files>`); there is no scribe agent
- Delegate stack detection to `stack-detector` agent
- Delegate spec synthesis to `spec-writer` agent
- Use ultrathink (extended thinking) for tech stack recommendations
- Collect and organize assets systematically
**You MUST NOT:**
- Write outside `${SESSION_PATH}/` (the spec itself is spec-writer's)
- Skip question categories
- Ask obvious questions already answered in spec
- Exceed iteration limits without user consent
</orchestrator_role>
<session_path_requirement>
**CRITICAL: SESSION_PATH Passing**
Every Agent delegation MUST start with SESSION_PATH prefix:
```
SESSION_PATH: ${SESSION_PATH}
[actual task instructions]
```
This ensures all agents write to the correct session directory.
</session_path_requirement>
<session_files>
The command keeps its own session files with Write. Four files, one rule each:
**`interview-log.md` — append only.** Read the file, then Write it back with the
new round added at the end. Never drop or rewrite an earlier round.
```markdown
## Round {N}
### Questions Asked
1. {question1} [TYPE: {context-independent|parameterized|context-deepening|context-enhancing}]
2. {question2} [TYPE: {type}]
### Answers
{user_answers}
### Triggers Identified
{triggers}
---
```
**`session-meta.json` — overwrite with the complete object.**
```json
{
"sessionId": "{SESSION_ID}",
"createdAt": "{timestamp}",
"type": "interview",
"interviewMode": "{focused|exploratory}",
"hasExistingSpec": true,
"status": "in_progress | spec_complete | completed",
"checkpoint": {
"phase": {current_phase},
"round": {current_round},
"coverage": { "{category}": {percent} },
"resumable": true
},
"lastUpdated": "{timestamp}"
}
```
**`focus-areas.md` — overwrite with current coverage.**
```markdown
# Focus Areas
| Category | Coverage | Questions Asked | Status |
|----------|----------|-----------------|--------|
| Functional Requirements | {%} | {N} | {status} |
| Non-Functional Requirements | {%} | {N} | {status} |
| User Experience | {%} | {N} | {status} |
| Edge Cases & Errors | {%} | {N} | {status} |
| Integration Points | {%} | {N} | {status} |
| Constraints & Trade-offs | {%} | {N} | {status} |
| Technical Preferences | {%} | {N} | {status} |
```
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.
- 23d ago Changed · +5 lines 50ce2b876d4c
- 25d ago Changed · -30 lines d989a0f50fee
- 1mo ago Changed · -36 lines 1ff1d61cff27
- 1mo ago Changed · +2 lines 708473b064b1
- 1mo ago First seen · 1,318 lines · 12 tokens per session scan A cf9e11d17b75
interview is a command published in the GitHub repository MadAppGang/magus (13 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 10,335 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to interview, differing in 363 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.