agentmods.dev

Python-Coding-Standards

Python coding rules for the BiRRe project, including supported syntax, typing, documentation, imports, linting, and function structure.

In plain words
What is it for?
Use them when creating or editing Python files in src/, especially when adding type hints, docstrings, imports, comments, or small focused functions.
Why use it?
They give contributors a shared standard for readable, testable, and consistently checked Python code.

Instructions file for GitHub Copilot

2 yesterday A scan 242 tokens original Unlicense
View the source file boecht/birre
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/boecht/birre/edit-python
Clone the repo
git clone --depth 1 https://github.com/boecht/birre

Made for: GitHub Copilot.

Per session 242 This file is loaded in full into every session.
When invoked 242 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.00242 $0.00242
Opus 5 $0.00121 $0.00121
Sonnet 5 $0.00048 $0.00048
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

Python-Coding-Standards 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/edit-python.instructions.md · 30 lines

What it actually says

When creating or editing Python code in src/:

  • Style and versions

    • Target Python 3.13 features and syntax.
    • Max line length: 100.

  • Types and docs

    • Add type hints for all functions and public methods.
    • Use Google-style docstrings for public APIs; keep private helpers concise.

  • Imports and linting

    • Keep imports sorted and grouped (ruff/isort rules).
    • Keep the code ruff-clean; prefer pyupgrade idioms.

  • Comments

    • Explain the "why" for non-obvious behavior and edge cases.
    • Avoid commented-out code and narrating the obvious.

  • Cohesion

    • One responsibility per function; prefer small, testable units.
    • Keep business logic in the appropriate layer/module.

Reference: CONTRIBUTING.md (Coding Standards) and copilot-instructions.md (Documentation Principles)

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 · 30 lines · 242 tokens per session scan A 7fc12122f616

Subscribe to this mod's changes

Python-Coding-Standards is an instructions file published in the GitHub repository boecht/birre (2 stars, last pushed yesterday), licensed Unlicense. It adds 242 tokens to every session, about $0.0012 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.

LanguagesWriting and docs
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