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/samueltauil/copilot-config-workshop/agents-mdgit clone --depth 1 https://github.com/samueltauil/copilot-config-workshopWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/samueltauil/copilot-config-workshop/agents-md)<a href="https://agentmods.dev/instructions/samueltauil/copilot-config-workshop/agents-md"><img src="https://agentmods.dev/badge/instructions/samueltauil/copilot-config-workshop/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00454 | $0.00454 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
copilot-config-workshop AGENTS.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 4d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This file provides guidance to AI coding agents working in this repository. Read this file before exploring the codebase or making any changes.
Repository Purpose
This repository is a workshop for learning how to configure GitHub Copilot. It contains seven exercises that follow the software development lifecycle. Each exercise builds a specialized Copilot agent (Planner, Architect, Developer, Tester, Orchestrator) while teaching a different configuration concept. There is no application code to build or deploy in the template itself; students generate the code during the exercises.
Repository Structure
exercises/- One subdirectory per exercise, each with aREADME.mdand optional starter code..github/copilot-instructions.md- Repository-wide Copilot Chat custom instructions..github/instructions/- Path-specific Copilot instruction files (.instructions.mdsuffix)..github/steps/- Step content files for the GitHub Skills framework..github/workflows/- GitHub Actions workflows that gate step progression.slides/index.html- Self-contained HTML slide deck (no build step required)..devcontainer/devcontainer.json- Dev container config for GitHub Codespaces.AGENTS.md- This file.README.md- Workshop landing page.LICENSE- MIT license.
Build and Test
This repository contains no build system, package manager, or test runner. There is nothing to compile, bundle, or execute.
To verify Markdown files, any standard Markdown linter may be used. No linter is pre-configured.
Conventions
- All prose uses US English.
- Markdown headings use ATX style (
#,##). - Code blocks include a language identifier (e.g.,
bash,js). - Cross-references within the repository use relative links.
- Exercise directories use zero-padded numbers (e.g.,
01,02).
Constraints
- Do not add build tools, package managers, or runtime dependencies.
- Do not rename or delete exercise directories.
- Do not modify the Reveal.js CDN links in
slides/index.html. - Keep this file under 60 lines.
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.
- 4d ago First seen · 50 lines · 454 tokens per session scan A 9602d0abfb66
copilot-config-workshop AGENTS.md is an instructions file published in the GitHub repository samueltauil/copilot-config-workshop (2 stars, last pushed 5mo ago), licensed MIT. It adds 454 tokens to every session, about $0.0023 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
vscode buildNext.instructions.md
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).
spec-kit AGENTS.md
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.
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.
langchain AGENTS.md
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.
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).
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.