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/natnew/awesome-prompt-engineering/copilot-instructionsgit clone --depth 1 https://github.com/natnew/Awesome-Prompt-EngineeringWrote 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/natnew/awesome-prompt-engineering/copilot-instructions)<a href="https://agentmods.dev/instructions/natnew/awesome-prompt-engineering/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/copilot-instructions.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.01416 | $0.01416 |
| Opus 5 | $0.00708 | $0.00708 |
| Sonnet 5 | $0.00283 | $0.00283 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
Awesome-Prompt-Engineering 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
About this repository
Awesome-Prompt-Engineering is a curated awesome list and learning hub for prompt engineering, context engineering, and AI agents. It is content, not an application: the deliverable is high-quality, well-organised Markdown, published to GitHub Pages via Jekyll.
README.md is the index and the main list. Topic pages (Basic_Prompting.md,
Advanced_Prompting.md, AI_Tools.md, Resources.md, Articles.md, and others)
hold the longer-form content. Contribution rules live in Contributing.md,
Workflow.md, and code-of-conduct.md.
How to treat the repository
- Treat every change as a documentation edit. There is no build, test, or runtime behaviour to reason about beyond Markdown rendering.
- Make the smallest change that achieves the goal. Do not reformat, reorder, or rewrite existing content that the task does not touch.
- Preserve the maintainer's voice and the structure already in place.
Contribution standard
The list is mature, so the bar is high. A good addition is unique, broadly
useful, durable, and non-promotional. Per Contributing.md, projects should be
more than 30 days old and have at least 60 stars. Prefer canonical sources
(official docs, the primary repository, the original paper or guide) over
marketing pages, mirrors, or aggregators.
Reviewing suggested additions
When assessing a new entry, check that it:
- is genuinely relevant to prompt engineering, context engineering, or AI agents;
- is not already listed — search the whole repository for the URL and the name before recommending it;
- links to a canonical, HTTPS source;
- has a neutral, factual description (no marketing taglines, no title-case), starting with a capital and ending with a full stop, and not beginning with "A" or "An";
- sits in the single best-fit existing category, added at the bottom of that category unless the section is alphabetised or otherwise ordered;
- matches the link style of the surrounding section (some lists use a hyphen, others an em dash — follow the local convention).
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.
- 5d ago First seen · 111 lines · 1,416 tokens per session scan A 69eb0fbaffd2
Awesome-Prompt-Engineering copilot-instructions.md is an instructions file published in the GitHub repository natnew/Awesome-Prompt-Engineering (108 stars, last pushed 1mo ago), licensed MIT. It adds 1,416 tokens to every session, about $0.0071 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.
Other instructions, from other repositories
awesome-awesome-ai CLAUDE.md
Claude Code instructions for dukeluo/awesome-awesome-ai, covering claude.md, what this repo is, curation rules (enforced by coderabbit), category boundaries and weekly audit workflow.
awesome-ai-scientists CLAUDE.md
Instructions for natnew/awesome-ai-scientists, covering claude.md, north star, resolver — load per task, first-pass workflow and stop conditions.
awesome-ai-scientists AGENTS.md
Instructions for natnew/awesome-ai-scientists, covering agents.md — operating protocol for ai agents, start here, repository north star, two surfaces, two formats and trust boundary.
apm python.instructions.md
Python development guidelines.
Awesome-Agentic-Engineering AGENTS.md
Instructions for natnew/Awesome-Agentic-Engineering, covering agents.md, repository north star, agent role, read order and repository facts.
Awesome-Agentic-Engineering readme-curation.instructions.md
Instructions for natnew/Awesome-Agentic-Engineering, covering readme curation, structure and ordering, descriptions, links and duplicates and after a content change.