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/pythongit clone --depth 1 https://github.com/franklesniak/copilot-repo-templateWhat 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.14305 | $0.14305 |
| Opus 5 | $0.07153 | $0.07153 |
| Sonnet 5 | $0.02861 | $0.02861 |
| Haiku 4.5 | $0.01431 | $0.01431 |
Grade A, and why
copilot-repo-template python.instructions.md scanned grade A with 2 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
from urllib.parse import urlsplit, urlunsplit Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- On Windows, when rendering the argv-style command line that matches Python's `subprocess` behavior, use `subprocess.list2cmdline()` behind an `os.name == "nt"` branch. This gives display parity with Python's Windows ar How it starts
The opening of the file, as written. The whole thing — 850 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Writing Style
Version: 1.10.20260704.0
Metadata
- Status: Active
- Owner: Repository Maintainers
- Last Updated: 2026-07-04
- Scope: Defines Python coding standards for all Python files in this repository, including modules, scripts, tests, and tooling. Covers style, structure, error handling, testing, and documentation requirements.
- Related: Repository Copilot Instructions
Purpose and Scope
This guide establishes the Python coding standards for the repository. Code MUST be maintainable, deterministic, and security-conscious. The style adapts to project constraints: stdlib-first, portability-first by default, shifting to modern-advanced when required by the technology stack (async frameworks, type-heavy APIs, etc.).
Note: This document uses RFC 2119 keywords (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY) to indicate requirement levels.
Executive Summary: Author Profile
The default style is a highly disciplined stdlib-first, portability-first approach. When code can reasonably run on a minimal, widely available Python baseline, it SHOULD: minimize dependencies, avoid unnecessary metaprogramming, and prefer clarity over cleverness.
This baseline is not dogma. When external constraints require modern Python (e.g., typing-heavy APIs, async I/O, Pydantic models, FastAPI), the style intentionally shifts to a modern-advanced posture.
Quick Reference Checklist
Layout and Formatting
- [All] MUST use 4 spaces; never tabs.
- [All] MUST follow PEP 8/PEP 257; line length target <= 100 (MAY exceed for URLs/long strings when readability wins).
- [All] MUST keep formatting tool-friendly: MUST NOT hand-align with extra whitespace.
- [All] SHOULD use f-strings for interpolation; SHOULD NOT use
%or.format()formatting except when required. - [All] SHOULD NOT rely on same-line implicit concatenation of adjacent string literals such as
f"a " "b"or"a" "b", and SHOULD NOT mix an f-string with an adjacent plain literal on the same line; a missing comma silently concatenates instead of erroring. Prefer one f-string or plain literal, and reserve adjacency for intentional multi-line wrapping described below. - [All] MUST NOT include trailing whitespace; files MUST end with a single newline.
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.
- 2d ago First seen · 850 lines · 14,305 tokens per session scan A 1478d320b9c9
copilot-repo-template python.instructions.md is an instructions file published in the GitHub repository franklesniak/copilot-repo-template (8 stars, last pushed 16d ago), licensed MIT. It adds 14,305 tokens to every session, about $0.0715 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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.