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 commands/gmickel/flow-next/interviewgit clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/gmickel/flow-next/interview)<a href="https://agentmods.dev/commands/gmickel/flow-next/interview"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/interview.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.00016 | $0.01033 |
| Opus 5 | $0.00008 | $0.00517 |
| Sonnet 5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00103 |
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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: This command MUST invoke the skill flow-next-interview
The ONLY purpose of this command is to call the flow-next-interview skill. You MUST use that skill now.
User input: $ARGUMENTS
Pass the user input to the skill. The skill handles the interview logic.
Optional flags
Scope (added in 1.1.0)
--scope=technical(default) — runs the technical pass only. Writes tech-owned sections (Architecture & Data Models,API Contracts,Edge Cases & Constraints, verifiable acceptance criteria). Preserves any populated business sections byte-for-byte. Reads business sections when present and cites them in the opener; silent when absent. This IS the 1.0.2 single-pass behavior — preserving as default means zero breaking change for solo devs.--scope=business— runs the business pass only. Writes biz-owned sections (Goal & Context,Boundaries,### Motivationunder## Decision Context, outcome acceptance criteria). Preserves technical-section bodies byte-for-byte; writes placeholder*Pending technical-scope interview pass.*ONLY under empty tech sections. BEFORE drafting biz questions, runs a project-docs investigation (README.md,CHANGELOG.md,STRATEGY.md,GLOSSARY.md,knowledge/decisions/,.flow/specs/index,docs/); items resolved by docs land in## Resolved via Project Docsand the user is NOT asked about things the project docs already define.--scope=both— runs the business pass first, then the technical pass in the same skill invocation. Same merge contract applies in each phase; auxiliary sections preserved across both.--biz— short alias for--scope=business.--tech— short alias for--scope=technical.
Conflicting flags (--biz --tech, --scope=business --tech, --scope=foo) error cleanly with an explicit "conflicting scope flags" or "invalid --scope value" message. R-IDs in ## Acceptance Criteria are append-only across scope passes — never renumbered, never replaced.
Doc-aware (existing)
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 · 44 lines · 16 tokens per session scan A da75e9d9640c
interview is a command published in the GitHub repository gmickel/flow-next (690 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,033 once invoked, about $0.0001 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 commands, from other repositories
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
objective-list
List all open objectives in the current repository.
flux-add
Quickly add a task to Flux from a brief description.
make
Create structured implementation plan in docs/plans/.
triage
Move tracker issues and external PRs through the triage state machine into agent-ready briefs. Use when triaging incoming issues, an external PR, or the backlog. Reads the tracker + label config written by /orc:setup.