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 attentiondotnet/davidondrej-skills --skill interview-style-doc-buildinggit clone --depth 1 https://github.com/attentiondotnet/davidondrej-skillsWrote 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/attentiondotnet/davidondrej-skills/interview-style-doc-building)<a href="https://agentmods.dev/skills/attentiondotnet/davidondrej-skills/interview-style-doc-building"><img src="https://agentmods.dev/badge/skills/attentiondotnet/davidondrej-skills/interview-style-doc-building/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/attentiondotnet/davidondrej-skills/interview-style-doc-building"><img src="https://agentmods.dev/badge/skills/attentiondotnet/davidondrej-skills/interview-style-doc-building.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.00065 | $0.00995 |
| Opus 5 | $0.00032 | $0.00498 |
| Sonnet 5 | $0.00013 | $0.00199 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
interview-style-doc-building 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview-Style Doc Building
The user's preferred mode for creating durable strategic docs. AI does NOT propose content — AI asks one question, the user answers, AI patches the file, AI asks the next question. The file IS the conversation's output, updated incrementally.
When to use
- Building a new SSOT file (life priorities, life vision, principles, frameworks, ranked lists).
- Filling out a structured doc the user explicitly wants to author themselves.
- Quarterly/annual reviews where the user's words go into the file.
NOT for: day planning (use day-plan), task triage (organize-tasks), or anything where AI proposes content first.
The Loop
- Create the file with a skeleton (header, sections, "to be filled in" placeholders). Single
write_filefor the new file. After this, NEVER overwrite — onlypatch. - Ask ONE question. Concise. Specific. Single-faceted. Open-ended where possible.
- Wait for the answer. Don't ask the next question yet.
- Patch the file with the user's answer in the correct section.
- Re-ask — next question, or follow-up if the answer was incomplete.
- Repeat until the file is complete.
Hard Rules
- One question at a time. Never dump multiple questions in a single message. The user has flagged this.
- Patch, don't overwrite. After the initial skeleton, use
patchfor every update. Neverwrite_fileto an existing doc. - Update the file BEFORE asking the next question. Order: receive answer → patch file → ask next question. Not the reverse.
- Lists from the user are UNORDERED SETS. When the user lists items in response to "which X should we cover?" or "what are the Ys?", that is a SET, not a ranking. Never infer rank, priority, or sequence from the order they typed them. If you need ordering, ask explicitly: "Which of these is #1?"
- Ask dynamics, not names. When the user references a person, don't ask "who is X?" — ask about the role/dynamic.
- No snark, no attitude, no filler. Concise questions, concise acknowledgments.
- No speculative additions. Don't invent sections, edge cases, or "anything else?" prompts unless the user asks.
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.
- 11d ago First seen · 71 lines · 65 tokens per session scan A 9a744c562f0c
interview-style-doc-building is a skill published in the GitHub repository attentiondotnet/davidondrej-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 995 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…