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/lugassawan/swe-workbench/interrogation-preludegit clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/interrogation-prelude)<a href="https://agentmods.dev/commands/lugassawan/swe-workbench/interrogation-prelude"><img src="https://agentmods.dev/badge/commands/lugassawan/swe-workbench/interrogation-prelude.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.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
interrogation-prelude 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 5d 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.
What it actually says
Interrogation mode. Before producing anything, resolve the mode:
- Explicit signal in the invocation is honored without asking. grill-me =
--grill, "grill me", or "grill-me mode". standard =--standard, "standard", or "quick". Strip the signal from $ARGUMENTS and record the resolved mode. - No explicit signal: ask via
AskUserQuestion— one question, header "Mode", options Standard (recommended, listed first) and Grill me. Standard description: "Lightweight clarify — a restatement and at most one question, then proceed." Grill-me description: "Relentlessly walk the decision tree one question at a time, each with a recommended answer, self-answering from the codebase where possible." Use the user's choice.
Standard mode: proceed with the command's existing lightweight clarify (a restatement and at most one clarifying question) — do not ask the mode question again.
Grill-me mode: activate swe-workbench:workflow-grill and run its interrogation loop to completion (exit on shared understanding or when the user says "proceed"). Then thread the emitted ## Resolved decisions block into the command's normal artifact/delegation step below — the same way a ticket-context summary is prepended — and continue as in standard mode.
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.
- 5d ago First seen · 9 lines · 0 tokens per session scan A 0ed07031428b
interrogation-prelude is a command published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 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-31.
Other commands, from other repositories
brooks-debt
Run a Brooks-Lint tech debt assessment.
brooks-review
Run a Brooks-Lint PR code review.
brooks-sweep
Run all Brooks-Lint analyses in one pass, auto-fix safe findings, confirm risky ones.
new-route
Scaffold a new API route end-to-end in the Go backend.
integrity
Fast integrity check on the current work. Feynman-style: what could invalidate this?
pr
Create a pull request with zetetic-standard review and documentation.