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 agentmods add instructions/thiagoguislotti/copilot-instructions/prgit 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/pr)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/pr"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/pr.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 | $0.00623 | $0.00623 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
copilot-instructions pr.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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Goals
Pull Request goals: clear title with concise scope; English language for title/description; reference related issues (e.g., Fixes #123); small, focused changes; align with repository guidelines.
Structure
Title [type: scope] short summary; Description with Context | Changes | Rationale | Risks | Testing | Docs | Breaking Changes | Migration; include Applied instructions section listing the instruction files actually followed.
Title Format
- Use imperative mood
- Keep <= 72 chars
- Include area prefix when helpful (e.g., Core, Tools, Samples)
- Avoid redundant words
- Prefer clarity over cleverness
[fix: backend] Add exponential retry with jitter to HttpClientFactory
[feat: database] Add keyset pagination and missing indexes
[chore: infra] Harden Dockerfile and add readiness probe
Description Content
Context (what/why); Changes (what changed at code/infra level); Rationale (why this approach); Risks (impact/mitigations); Testing (how validated: unit/integration/E2E); Docs (README/CHANGELOG updated); Breaking Changes (yes/no and details); Migration (steps if any).
Context: users face transient 502/504
Changes: add Polly WaitAndRetry with jitter to HttpClientFactory
Rationale: improve resilience per backend.instructions.md
Risks: excessive retries mitigated by maxAttempts=3 and timeout
Testing: unit tests added + integration smoke
Docs: CHANGELOG updated
Breaking Changes: no
Migration: none
Applied Instructions
List paths like .github/instructions/backend.instructions.md; .github/instructions/dotnet-csharp.instructions.md; summarize how each was applied; include any deviations and justification.
Applied instructions:
- .github/instructions/backend.instructions.md
- .github/instructions/dotnet-csharp.instructions.md
- .github/instructions/ci-cd-devops.instructions.md
Applied: resilience (retry/jitter), CancellationToken, tests and pipeline gates
Deviations: none
Quality Checklist
- Build and tests pass
- Lints/formatting clean
- Security checks considered
- No secrets in diff
- Performance implications reviewed
- Consistent namespaces and folder structure
- UTF-8 without BOM
- No trailing blank line at EOF in modified files
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 · 69 lines · 623 tokens per session scan A 035ee3e76ce7
copilot-instructions pr.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 623 tokens to every session, about $0.0031 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.