Borrowing it
Nothing to install: this file belongs to gosha70/code-copilot-team. 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/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/clarification-protocol.instructions.mdgit clone --depth 1 https://github.com/gosha70/code-copilot-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/instructions/gosha70/code-copilot-team/clarification-protocol)<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/clarification-protocol"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/clarification-protocol.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.01663 | $0.01663 |
| Opus 5 | $0.00831 | $0.00831 |
| Sonnet 5 | $0.00333 | $0.00333 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
code-copilot-team clarification-protocol.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 3d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarification Protocol
Rules for when to ask clarifying questions instead of making assumptions.
Always Ask Before Implementing
Data Model Decisions
Before creating or modifying entity fields, confirm with the user:
- Field granularity: Single combined field vs split into components? (e.g., one field vs multiple for compound values)
- Normalization: Flat fields on the parent entity vs a separate related entity?
- Status/type fields: Enum values — which states are needed? Will they change over time?
- Relationships: One-to-many vs many-to-many? Optional vs required?
- Audit fields: Which standard fields? (
createdAt,updatedAt,deletedAt,createdBy?)
Don't assume the simplest representation. Compound fields that seem fine early often need to be split later for filtering, sorting, or reporting.
Output Format Decisions
Before generating reports, exports, or formatted output:
- Column names: Confirm exact headers (e.g., "Count" vs "Total" vs "Amount").
- Row structure: What does each record represent (per day? per item? per transaction?)?
- Grouping: How should data be aggregated?
- File format: CSV, JSON, PDF, or in-app table?
Generating the wrong format costs a full rebuild. Asking costs one message.
UI Layout Decisions
Before implementing visual components:
- Image positioning: Left/right of text? Above/below? Full-width banner?
- Section ordering: What content is above the fold? What can the user scroll to?
- Interactive elements: Buttons, toggles, dropdowns — confirm behavior on click.
- Responsive behavior: Mobile-first or desktop-first? What collapses on small screens?
Auth & Access Decisions
Before implementing authentication or authorization:
- Auth strategy: Password-based? Magic link? OAuth? Passkeys?
- Who can access what: Admin-only sections? Guest access? Role-based?
- Account requirement: Is registration mandatory or optional?
- Session behavior: How long should sessions last? Remember me?
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.
- 3d ago First seen · 160 lines · 1,663 tokens per session scan A 93f33dab4656
code-copilot-team clarification-protocol.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 1,663 tokens to every session, about $0.0083 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 instructions, from other repositories
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).
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.
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.
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).
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.