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/franklesniak/copilot-repo-template/gitattributesgit 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/gitattributes)<a href="https://agentmods.dev/instructions/franklesniak/copilot-repo-template/gitattributes"><img src="https://agentmods.dev/badge/instructions/franklesniak/copilot-repo-template/gitattributes.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.03843 | $0.03843 |
| Opus 5 | $0.01921 | $0.01921 |
| Sonnet 5 | $0.00769 | $0.00769 |
| Haiku 4.5 | $0.00384 | $0.00384 |
Grade A, and why
copilot-repo-template gitattributes.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 5d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.gitattributes Rules
Version: 1.4.20260617.0
Metadata
- Status: Active
- Owner: Repository Maintainers
- Last Updated: 2026-06-17
- Scope: Applies to any
.gitattributesfile in repositories that adopt these instructions, independent of programming language. Governs how committed text artifacts, linter-enforced LF file families, template-managed text formats, ordinary binary declassification, and opt-in Git LFS-managed binaries are protected against platform-dependent checkout rewriting or incorrect Git attribute handling. - Related: Repository Copilot Instructions
Purpose and Scope
This file defines the normative rule for entries in .gitattributes that protect byte-exact text artifacts, linter-enforced LF file families, and template-managed text formats from platform-dependent line-ending rewriting. It also distinguishes ordinary binary declassification from opt-in Git LFS-managed binary attributes. It applies to every .gitattributes file in any repository that adopts these instructions, regardless of the programming languages used in the repository.
Note: This document uses RFC 2119 keywords (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY) to indicate requirement levels.
Quick Reference Checklist
- [All] Any committed text file whose identity is its exact byte sequence MUST be pinned to LF in
.gitattributesusing a path pattern as specific as practical. See Rule: Pin Byte-Exact Text Artifacts to LF. - [All] Any committed text file family whose repository-enforced linter or validator requires LF line endings MUST be pinned to LF in
.gitattributes. See Rule: Pin Linter-Enforced LF File Families to LF. - [Templates] Common template-managed text formats that are edited or pruned across platforms SHOULD be pinned to LF when host-dependent CRLF conversion would create broad, non-semantic churn. See Rule: Pin Template-Managed Text Formats to LF.
- [All] Ordinary binary formats that should remain in Git but must not receive text conversion SHOULD use Git's built-in
binarymacro, while formats intentionally stored through Git LFS MUST use explicit LFS attributes. See Rule: Separate Ordinary Binary Overrides From Git LFS Tracking.
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.
- 5d ago First seen · 204 lines · 3,843 tokens per session scan A 60b30c35c780
copilot-repo-template gitattributes.instructions.md is an instructions file published in the GitHub repository franklesniak/copilot-repo-template (8 stars, last pushed 19d ago), licensed MIT. It adds 3,843 tokens to every session, about $0.0192 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
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).
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.
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.
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).