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 skills add bdfinst/agentic-dev-team --skill design-interrogationgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/design-interrogation)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/design-interrogation"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/design-interrogation/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/skills/bdfinst/agentic-dev-team/design-interrogation"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/design-interrogation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00114 | $0.00903 |
| Opus 5.5 | $0.00046 | $0.00361 |
| Sonnet 5.5 | $0.00023 | $0.00181 |
| Haiku 4.5 | $0.00011 | $0.00090 |
Grade A, and why
design-interrogation 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Interrogation
Overview
Walk every branch of a decision tree until all decisions are resolved. The goal is not to produce an artifact — it's to force the developer to think through decisions they'd otherwise skip. Good designs fail not from what was considered, but from what wasn't.
When to Use
- Before committing to a plan (Research phase, before
/plan) - After a design doc is drafted but before implementation
- When the user says "grill me" or "stress-test this"
- When a plan has implicit assumptions that need to be surfaced
How It Works
1. Identify the Decision Surface
Read the plan, design doc, spec, or description. Identify every decision point — explicit ones the user already made, and implicit ones hiding behind assumptions. Look for:
- Unstated assumptions: "We'll use X" without explaining why not Y
- Vague scope boundaries: "We'll handle that later" — when is later?
- Missing error paths: What happens when the happy path breaks?
- Integration seams: Where does this design touch other systems?
- Scale implications: Does this work for 10 users? 10,000? 10 million?
- Migration paths: How do you get from the current state to the proposed state?
2. Walk the Decision Tree
Ask questions one at a time. For each question:
- State the decision that needs to be made
- Provide your recommended answer with reasoning
- If the question can be answered by exploring the codebase, explore it yourself instead of asking the user
- Wait for the user's response before moving to the next question
Follow dependency order — resolve foundational decisions before asking about things that depend on them. If an answer to one question invalidates a previous decision, flag it.
3. Go Deep, Not Wide
Don't ask surface-level questions. Push into the uncomfortable territory:
- "You said you'd use a queue here — what happens when the queue fills up?"
- "This assumes the API is always available. What's the degradation strategy?"
- "You've designed for creation but not deletion. Is that intentional?"
- "Three services share this model. Who owns the schema?"
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 · 90 lines · 114 tokens per session scan A e4a9e75eab83
design-interrogation is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 114 tokens to every session and 903 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…