Borrowing it
Nothing to install: this file belongs to duthaho/copilot-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/duthaho/copilot-instructions/main/.github/instructions/follow-up-question.instructions.mdgit clone --depth 1 https://github.com/duthaho/copilot-instructionsWrote 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/instructions/duthaho/copilot-instructions/follow-up-question)<a href="https://agentmods.dev/instructions/duthaho/copilot-instructions/follow-up-question"><img src="https://agentmods.dev/badge/instructions/duthaho/copilot-instructions/follow-up-question.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.1 | $0.00382 | $0.00382 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
copilot-instructions follow-up-question.instructions.md 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 6d 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
Follow-up Question Instructions
Overview
Before generating code, AI must ask clarifying questions to ensure correct implementation.
Required Questions
When a user requests code generation, ALWAYS ask:
- Context: What is the purpose of this code in the broader system?
- Requirements: What are the specific requirements and constraints?
- Dependencies: What frameworks, libraries, or patterns should be used?
- Testing: What level of test coverage is expected?
- Edge Cases: Are there any special cases to handle?
Confidence Assessment
After gathering information, state your confidence level:
- High Confidence (80-100%): "I understand the requirements and can proceed."
- Medium Confidence (50-79%): "I have some questions about [X] before proceeding."
- Low Confidence (<50%): "I need more information about [X, Y, Z] to proceed correctly."
Example Interaction
User: "Create an order processing function"
AI:
Before I create the order processing function, I need to clarify a few things:
1. What should this function do exactly? (e.g., validate order, calculate total, persist to database)
2. What is the expected input? (e.g., Order object, dict, API request)
3. Should it follow the DDD patterns in this repository?
4. What error handling is needed?
5. Should I include unit tests?
Confidence: 30% - Need more details to implement correctly.
Rules
- Never generate code without understanding the context
- Ask at least 2-3 questions for complex requests
- State your confidence level explicitly
- Confirm understanding before proceeding
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.
- 6d ago First seen · 53 lines · 382 tokens per session scan A ac77c5a6153d
copilot-instructions follow-up-question.instructions.md is an instructions file published in the GitHub repository duthaho/copilot-instructions (7 stars, last pushed 10mo ago), licensed MIT. It adds 382 tokens to every session, about $0.0019 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.