Borrowing it
Nothing to install: this file belongs to natnew/Awesome-Prompt-Engineering. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/natnew/Awesome-Prompt-Engineering/main/.github/instructions/readme-curation.instructions.mdgit 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/readme-curation)<a href="https://agentmods.dev/instructions/natnew/awesome-prompt-engineering/readme-curation"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/readme-curation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/natnew/awesome-prompt-engineering/readme-curation"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/readme-curation.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00432 | $0.00432 |
| Opus 5.5 | $0.00173 | $0.00173 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
Awesome-Prompt-Engineering readme-curation.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 1mo 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.
What it actually says
Curating the main list (README.md)
README.md is the index and the primary awesome list. Edits here should be
careful and minimal.
Structure and ordering
- Keep the existing section order and headings. Do not introduce, rename, or reorder categories as part of adding an entry.
- Place each new entry in the single best-fit existing category.
- Add entries to the bottom of a category, unless that section is alphabetised or otherwise ordered — then follow the existing order.
- Match the link style of the surrounding section. Some lists use a hyphen
(
[name](link) - Description.) and others an em dash (—); follow the local convention rather than imposing one.
Descriptions
- Keep them short, neutral, and factual — a plain statement of what the resource is, not a marketing tagline.
- Start with a capital letter and end with a full stop.
- Do not begin with "A" or "An", and do not use title-case.
- Avoid time-sensitive wording ("new", "latest", "now supports"). The dated Announcements table is the only place for time-stamped entries.
Links
- HTTPS only.
- Prefer the canonical source: the project's GitHub repository, official documentation, or the primary paper — not a marketing site, mirror, or package-registry page.
Before adding
- Confirm the resource is relevant to prompt engineering, context engineering, or AI agents.
- Search the whole repository for the URL and the name first — duplicates are the most common problem.
- If it resembles an existing entry, only suggest it if it is demonstrably better, and say why.
Protected areas — do not edit casually
Badges, the Announcements table, contributor tables, and anything between
<!-- ALL-CONTRIBUTORS-LIST:START --> and <!-- ALL-CONTRIBUTORS-LIST:END -->.
Leave these unless the maintainer explicitly asks.
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.
- 1mo ago First seen · 51 lines · 432 tokens per session scan A aead9ea8e60f
Awesome-Prompt-Engineering readme-curation.instructions.md is an instructions file published in the GitHub repository natnew/Awesome-Prompt-Engineering (114 stars, last pushed 5d ago), licensed MIT. It adds 432 tokens to every session, about $0.0017 per session on Opus 5.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
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).
next.js AGENTS.md
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, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.