Borrowing it
Nothing to install: this file belongs to franklesniak/copilot-repo-template. 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/franklesniak/copilot-repo-template/main/.github/instructions/docs.instructions.mdgit clone --depth 1 https://github.com/franklesniak/copilot-repo-templateWrote 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/franklesniak/copilot-repo-template/docs)<a href="https://agentmods.dev/instructions/franklesniak/copilot-repo-template/docs"><img src="https://agentmods.dev/badge/instructions/franklesniak/copilot-repo-template/docs.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.13443 | $0.13443 |
| Opus 5 | $0.06721 | $0.06721 |
| Sonnet 5 | $0.02689 | $0.02689 |
| Haiku 4.5 | $0.01344 | $0.01344 |
Grade A, and why
copilot-repo-template docs.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 6d 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writing Style
Version: 1.6.20260623.0
Metadata
- Status: Active
- Owner: Repository Maintainers
- Last Updated: 2026-06-23
- Scope: Defines documentation standards for Markdown (
**/*.md) and Cursor Markdown rule (**/*.mdc) files in this repository, including specs, design docs, runbooks, ADRs, instruction files, and developer documentation. Does not cover code comments or inline documentation in source files. - Related: Repository Copilot Instructions
Purpose and Scope
Documentation in this repository is treated as a first-class engineering artifact, not an afterthought. Docs are expected to function as:
- A contract (what the system does, does not do, and why)
- A design record (how it works, constraints, trade-offs, failure modes)
- A maintenance tool (how to safely change and operate it without regressions)
This file governs all Markdown (**/*.md) and Cursor Markdown rule (**/*.mdc) documentation in this repository, including README.md, docs/**, ADRs, runbooks, release notes, instruction files under .github/instructions/, and Cursor project rules under .cursor/rules/.
Repository Portability
This guide is intended to remain usable when copied into downstream template-derived repositories and into independent, non-template repositories. Requirements apply when the described file type, publishing surface, repository feature, toolchain, or validation hook exists in the adopting repository. Rules for absent ecosystems or absent repository features are inactive until that repository intentionally adopts the relevant files or tooling.
Repository-specific paths, workflow names, validation commands, and examples SHOULD be replaced with repository-local equivalents during adoption. If a referenced companion guide, workflow, schema directory, or validator is not present, authors SHOULD either remove that reference or phrase the guidance conditionally so the file remains accurate on its own.
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.
- 6d ago First seen · 493 lines · 13,443 tokens per session scan A 4a099d33d454
copilot-repo-template docs.instructions.md is an instructions file published in the GitHub repository franklesniak/copilot-repo-template (8 stars, last pushed 20d ago), licensed MIT. It adds 13,443 tokens to every session, about $0.0672 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.