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/duthaho/copilot-instructions/coding-style-pythongit clone --depth 1 https://github.com/duthaho/copilot-instructionsWhat 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.02099 | $0.02099 |
| Opus 5 | $0.01050 | $0.01050 |
| Sonnet 5 | $0.00420 | $0.00420 |
| Haiku 4.5 | $0.00210 | $0.00210 |
Grade A, and why
copilot-instructions coding-style-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 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.
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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Coding Style Instructions
Overview
This instruction file enforces Python coding standards based on PEP 8, type hints, and modern Python practices.
Code Formatting
Use Black for automatic formatting and Ruff for linting.
# pyproject.toml
[tool.black]
line-length = 100
target-version = ['py311']
[tool.ruff]
line-length = 100
target-version = "py311"
select = ["E", "F", "I", "N", "W", "UP"]
Type Hints
MANDATORY: All public functions, methods, and classes must have type hints.
✅ Good:
from typing import Optional, List
from uuid import UUID
def get_customer_orders(customer_id: UUID, limit: int = 10) -> List[Order]:
"""Retrieve customer orders with type hints."""
pass
class OrderService:
def __init__(self, repository: OrderRepository) -> None:
self._repository = repository
def create_order(self, customer_id: UUID) -> Order:
return Order(id=uuid4(), customer_id=customer_id)
❌ Bad:
def get_customer_orders(customer_id, limit=10): # No type hints
pass
Naming Conventions
- Classes: PascalCase (
OrderService,CustomerRepository) - Functions/Methods: snake_case (
calculate_total,get_by_id) - Constants: UPPER_SNAKE_CASE (
MAX_RETRIES,DEFAULT_TIMEOUT) - Private attributes: Leading underscore (
_internal_state) - Module names: snake_case (
order_service.py)
# Good naming
class OrderProcessor:
MAX_BATCH_SIZE = 100
def __init__(self) -> None:
self._cache: dict[str, Order] = {}
def process_orders(self, orders: List[Order]) -> None:
pass
Docstrings
Use Google-style docstrings for public APIs:
def calculate_discount(
base_price: float,
discount_percentage: float,
customer_tier: str
) -> float:
"""Calculate discounted price based on customer tier.
Args:
base_price: The original price before discount
discount_percentage: Discount percentage (0-100)
customer_tier: Customer tier ("REGULAR", "PREMIUM", "VIP")
Returns:
The final price after applying discount
Raises:
ValueError: If discount_percentage is not between 0 and 100
Example:
>>> calculate_discount(100.0, 10.0, "PREMIUM")
90.0
"""
if not 0 <= discount_percentage <= 100:
raise ValueError("Discount must be between 0 and 100")
return base_price * (1 - discount_percentage / 100)
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 · 378 lines · 2,099 tokens per session scan A fde3525b4495
copilot-instructions coding-style-python.instructions.md is an instructions file published in the GitHub repository duthaho/copilot-instructions (7 stars, last pushed 10mo ago), licensed MIT. It adds 2,099 tokens to every session, about $0.0105 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
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
apex-accelerator python.instructions.md
Python coding conventions for diagram generation, MCP servers, and tooling scripts.
apm python.instructions.md
Python development guidelines.
llm-ide-rules python-app.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
llm-ide-rules pytest-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.
llm-ide-rules python.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering python, package management, typing, data manipulation and date & datetime.