discovery copilot-instructions.md

Project instructions for a Python application that repeatedly checks APIs and runs in local, Docker, or Azure environments.

In plain words
What is it for?
Use them when writing Python functions, managing settings from command-line arguments or environment variables, handling files, and adding reliable API polling.
Why use it?
They give consistent rules for code style, configuration, file handling, API retries, and portability across environments.

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/microsoft/discovery/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/microsoft/discovery

Made for: GitHub Copilot.

Per session 2,104 This file is loaded in full into every session.
When invoked 2,104 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.02104 $0.02104
Opus 5 $0.01052 $0.01052
Sonnet 5 $0.00421 $0.00421
Haiku 4.5 $0.00210 $0.00210

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

Security

Grade A, and why

discovery copilot-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.

utilities/supercomputer-cli/.github/copilot-instructions.md · 244 lines

How it starts

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

Copilot Instructions for Python API Polling Project

Project Context

This is a Python-based API polling application designed for portability across different environments (local development, Docker containers, and cloud platforms like Azure Discovery).

Code Style Guidelines

Python Standards

  • Use Python 3.9+ features and type hints for all function signatures
  • Follow PEP 8 naming conventions (snake_case for functions/variables, UPPER_CASE for constants)
  • Use pathlib.Path instead of os.path for file operations
  • Prefer f-strings for string formatting
  • Add docstrings to all functions using Google style format

Configuration Management

  • Use environment variables for all configuration with sensible defaults
  • Support both .env files (via python-dotenv) and direct environment variables
  • Implement configuration precedence: CLI args > env vars > config files > defaults
  • Use pydantic Settings classes for configuration validation when possible

API Interaction Patterns

# Always use exponential backoff for retries
from tenacity import retry, stop_after_attempt, wait_exponential

@retry(stop=stop_after_attempt(3), wait=wait_exponential(min=1, max=10))
async def call_api(endpoint: str, **kwargs) -> dict:
    """Make API call with automatic retry logic."""
    pass

Polling Implementation

  • Use async/await patterns with asyncio for efficient polling
  • Implement configurable poll intervals with jitter to avoid thundering herd
  • Always include timeout mechanisms
  • Log poll attempts and results at appropriate levels (DEBUG for success, WARNING for retries, ERROR for failures)

Error Handling

  • Use custom exception classes for different error scenarios
  • Always catch and log exceptions at the appropriate level
  • Implement graceful shutdown handling (SIGTERM, SIGINT)
  • Return meaningful exit codes (0=success, 1=general error, 2=config error, 3=connection error)

Logging

import logging
import sys

# Configure structured logging
logging.basicConfig(
    level=logging.INFO,
    format='[%(asctime)s] [%(name)s] [%(levelname)s] %(message)s',
    handlers=[logging.StreamHandler(sys.stdout)]
)

Read the full file on GitHub · 244 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. 2d ago First seen · 244 lines · 2,104 tokens per session scan A 2f69e03ab3a3

Subscribe to this mod's changes

discovery copilot-instructions.md is an instructions file published in the GitHub repository microsoft/discovery (233 stars, last pushed 4d ago), licensed MIT. It adds 2,104 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-30.

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