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/antiotaku/github-copilot-instructions/uvgit clone --depth 1 https://github.com/antiotaku/github-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.08176 | $0.08176 |
| Opus 5 | $0.04088 | $0.04088 |
| Sonnet 5 | $0.01635 | $0.01635 |
| Haiku 4.5 | $0.00818 | $0.00818 |
Grade C, and why
github-copilot-instructions uv.instructions.md scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh-add ~/.ssh/id_rsa How it starts
The opening of the file, as written. The whole thing — 1,331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uv Project and Package Management Instructions
Overview
You MUST use uv as the primary Python package manager and project management tool. uv is an extremely fast Python package installer and resolver written in Rust that serves as a drop-in replacement for pip, pip-tools, and virtualenv.
Core Principles
- You WILL ALWAYS use uv for Python dependency management instead of pip, poetry, or conda
- You MUST create and maintain pyproject.toml files for all Python projects
- You WILL use uv's built-in virtual environment management
- You MUST leverage uv's lockfile functionality for reproducible builds
- You WILL use uv for Python version management when needed
Project Initialization
New Python Project
# Create a new Python project with uv
uv init my-project
cd my-project
# Or initialize in existing directory
uv init
New Python Package
# Create a new Python package (installable library)
uv init --package my-package
cd my-package
# Create package in existing directory
uv init --package
# Create package with specific Python version
uv init --package my-package --python 3.11
New Python Library
# Create a new Python library (for distribution)
uv init --lib my-library
cd my-library
# Create library in existing directory
uv init --lib
# Create library with specific build backend
uv init --lib my-library --build-backend hatchling
Project Template Options
# Create application project (default)
uv init my-app
# Create package project (installable via pip)
uv init --package my-package
# Create library project (for PyPI distribution)
uv init --lib my-library
# Create with custom package name
uv init --name custom-name my-project
# Create without Git initialization
uv init --no-git my-project
# Create with specific Python requirement
uv init --python ">=3.9" my-project
Project Type Selection Guide
Application Project (uv init)
- Use for standalone applications, scripts, or web services
- Creates basic project structure with src/ layout
- Includes basic pyproject.toml configuration
- Best for projects that won't be distributed as packages
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.
- yesterday First seen · 1,331 lines · 8,176 tokens per session scan C 1fa08104d40f
github-copilot-instructions uv.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 8,176 tokens to every session, about $0.0409 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). 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.
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).
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.
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).
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.
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.