Borrowing it
Nothing to install: this file belongs to ThiagoGuislotti/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/ThiagoGuislotti/copilot-instructions/main/.github/instructions/authoritative-sources.instructions.mdgit clone --depth 1 https://github.com/ThiagoGuislotti/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/thiagoguislotti/copilot-instructions/authoritative-sources)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/authoritative-sources"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/authoritative-sources.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.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
copilot-instructions authoritative-sources.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 7d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
- Define the single repository-wide policy for resolving technical uncertainty with repository context first and authoritative documentation second.
- Keep the stack-to-domain mapping centralized in
.github/governance/authoritative-source-map.json. - Prevent duplicated official documentation domain lists across domain instruction files.
Resolution Order
- Use repository context first for project-specific rules, architecture, scripts, templates, conventions, and operational decisions.
- If the question depends on external platform, framework, library, API, or tool behavior, consult the official documentation for the active stack.
- If the official documentation is incomplete, consult the official maintainer repository or project documentation.
- Community sources are fallback only and must not override repository rules or official vendor guidance.
When External Lookup Is Required
- Version-specific or recently changed behavior
- Security, authentication, authorization, privacy, compliance, or cryptography guidance
- Infrastructure, platform, SDK, CLI, framework, or tooling behavior
- Performance tuning guidance that depends on vendor/runtime specifics
- API behavior, limits, defaults, or deployment/runtime constraints
Official Source Map
- Use
.github/governance/authoritative-source-map.jsonas the single source of truth for stack-specific official domains. - Prefer the narrowest matching stack entry instead of a broad vendor-wide search.
- Do not copy or restate official documentation domain lists inside other instruction files unless an exception is explicitly justified.
Response Rules
- State whether the conclusion came from repository context, official documentation, or inference.
- If repository context conflicts with official documentation, follow repository context for internal rules and use official documentation only for external platform behavior.
- For high-risk topics, prefer authoritative documentation over memory.
- When authoritative documentation is unavailable or insufficient, say so explicitly before relying on inference or community material.
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.
- 7d ago First seen · 54 lines · 660 tokens per session scan A dd62a0be211a
copilot-instructions authoritative-sources.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 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.