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 gosha70/code-copilot-team --skill clarification-protocolgit 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/skills/gosha70/code-copilot-team/clarification-protocol)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/clarification-protocol"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/clarification-protocol/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/gosha70/code-copilot-team/clarification-protocol"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/clarification-protocol.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.00025 | $0.01686 |
| Opus 5.5 | $0.00010 | $0.00674 |
| Sonnet 5.5 | $0.00005 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
clarification-protocol 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 — 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.
- 1mo ago First seen · 160 lines · 25 tokens per session scan A bf94d6c60fa1
clarification-protocol is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 1,686 once invoked, about $0.0001 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
agent-deck
Helper scripts live in this skill's scripts/ folder. Resolve them from the base directory shown when the skill loaded, not from the user's project.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
deck-repro
Reproduce agent-deck bugs from an issue, transcript excerpt, or description in an isolated environment, and prove fixes with the same reproduction and a regression test. Use for a concrete agent-deck issue or candidate, verifying a fix, preparing a contributor bug-fix PR, or when deck-retro passes a candidate. Broad…
codex-log-guard
Diagnose excessive Codex local SQLite diagnostic log writes with read-only evidence by default. Use when a user mentions logs2.sqlite, logs2.sqlite-wal, blockloginserts, SSD/TBW wear, or explicitly asks to protect, clean up, verify, or restore Codex diagnostic logging.
milvus-integration
Milvus distributed vector database configuration for large-scale RAG applications.