github-copilot-instructions python.instructions.md

A set of Python coding rules covering supported versions, project structure, packaging, type hints, testing, and everyday style.

In plain words
What is it for?
Use it when creating, reviewing, or changing Python packages and applications, especially those using pyproject.toml, uv, or hatchling.
Why use it?
It gives the coding agent one consistent standard to follow, reducing debates and inconsistent code across Python projects.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/antiotaku/github-copilot-instructions/python
Clone the repo
git clone --depth 1 https://github.com/antiotaku/github-copilot-instructions

Made for: GitHub Copilot.

Per session 3,227 This file is loaded in full into every session.
When invoked 3,227 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03227 $0.03227
Opus 5 $0.01614 $0.01614
Sonnet 5 $0.00645 $0.00645
Haiku 4.5 $0.00323 $0.00323

Measured yesterday against content hash a6a5508b22ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-copilot-instructions python.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 yesterday.

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.

.github/instructions/python.instructions.md · 416 lines

How it starts

The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Python Coding Conventions & Style Guide

0. Overview

This document outlines the coding conventions and style guidelines for Python projects. It covers Python version policies, project structure, type hinting, coding practices, testing, and practical examples.

1. Python Version Policy

  • Minimum Supported Version: Python 3.10
  • Recommended Version: Python 3.11 or later
  • Deprecated Versions: Python 3.9 and earlier
  • Unsupported Versions: Python 2.x
  • MUST NOT use deprecated or obsolete Python features.

2. Default Coding Style: Google Python Style Guide

  • Follow the Google Python Style Guide as the baseline for coding style.
  • If there are conflicts between Google Style and Other Guidelines, prefer Google Style unless there is a compelling reason not to.

3. Project Structure & Packaging

Project Structure

  • PEP 420: Use implicit namespace packages for multi-directory packages.

Project Packaging

  • PEP 517/518: Use pyproject.toml for build system configuration.
    • Use uv and hatchling for building and packaging.
  • PEP 621: Use pyproject.toml for project metadata (name, version, description, authors, license, dependencies).
  • PEP 561: For libraries, include type information by adding a py.typed file in the package directory.

Single application Example

For a single application, the project name should be the same as the package name. For example, a project named myapp would have the following structure:

myapp/                       # Project root, `myapp` is the project name
├── src/                     # Source code directory
│   └── myapp/               # Package namespace from project name
│       ├── __init__.py      # Package initializer
│       ├── main.py          # Main application module
│       └── py.typed         # Marker file for type information
├── tests/                   # Tests directory
│   ├── __init__.py          # Test package initializer
│   └── test_main.py         # Example test module
└── pyproject.toml           # Build system and project metadata

Read the full file on GitHub · 416 lines

Changes

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.

  1. yesterday First seen · 416 lines · 3,227 tokens per session scan A a6a5508b22ce

Subscribe to this mod's changes

github-copilot-instructions python.instructions.md is an instructions file published in the GitHub repository antiotaku/github-copilot-instructions (1 stars, last pushed 10mo ago), licensed MIT. It adds 3,227 tokens to every session, about $0.0161 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.

Related

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens