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/readme.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/readme)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/readme"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/readme/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/instructions/thiagoguislotti/copilot-instructions/readme"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/readme.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.00460 | $0.00460 |
| Opus 5.5 | $0.00184 | $0.00184 |
| Sonnet 5.5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
copilot-instructions readme.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 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Baseline
Use .github/templates/readme-template.md as the default starting point.
This file defines the generic README baseline only.
If a higher-priority repository-specific README instruction exists, that file may narrow or override section set, order, and examples policy.
Do not assemble a README directly from this instruction file; use the template for concrete structure and placeholders.
README Types
Repository README
Focus on repository overview, navigation, build/test entry points, contribution guidance, dependencies, and references. Do not force package-installation sections into the root README when repository-specific rules say otherwise.
Package or App README
Prefer these sections when they are applicable: Introduction, Table of Contents or Contents, Installation, Quick Start, Usage Examples, API Reference, Build and Tests, Contributing, Dependencies, References. If a section does not apply, remove it instead of filling it with weak placeholder text.
Content Expectations
- Introduction explains problem, context, and technical approach.
- Features section, when present, uses checkmark bullets.
- Table of Contents or Contents links the main sections that actually exist in the file.
- When stable subsections exist under a section,
Contentsmust include nested anchor links for those subsection entries in the same order. - The default README template must keep nested
Contentsitems forUsage ExamplesandAPI Referencesubsections unless those subsections are intentionally removed from the document. - Installation shows real setup commands and package references.
- Quick Start stays minimal and runnable.
- Usage Examples cover typical and advanced scenarios with real code.
- API Reference uses real signatures, parameters, and returns.
- Build and Tests shows real repository commands when the README type requires operational guidance.
- References link to changelog, related packages, docs, issues, or external technical 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.
- 1mo ago First seen · 41 lines · 460 tokens per session scan A eafc04dd8f3a
copilot-instructions readme.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 3mo ago), licensed MIT. It adds 460 tokens to every session, about $0.0018 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-08-31.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).