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/contribution-review.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/contribution-review)<a href="https://agentmods.dev/instructions/natnew/awesome-prompt-engineering/contribution-review"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/contribution-review/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/contribution-review"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/contribution-review.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.00403 | $0.00403 |
| Opus 5.5 | $0.00161 | $0.00161 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
Awesome-Prompt-Engineering contribution-review.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
Reviewing pull requests and issues
This is a community list. Reviews should keep the bar high while staying welcoming and low-friction. Use a calm, respectful tone.
Tone
- Thank the contributor for their time.
- Be concise and specific. When something needs changing, name the rule and link
the relevant guide (
Contributing.md,Workflow.md). - Never gatekeep harshly. Assume good faith.
How to respond
- Accept when the entry is relevant, the link is a canonical HTTPS source, the description follows the rules, it sits in the right category, and it is not a duplicate.
- Fix small issues yourself (wording, casing, trailing whitespace, hyphen vs em dash, slightly-off placement) rather than asking the contributor to re-push.
- Request changes only when the contributor's input is genuinely needed: a broken or duplicate link, missing rationale for why it beats an existing entry, unrelated changes bundled together, or an objective rule they should correct.
- Decline politely when a submission is promotional or self-promotion only, out of scope, or below the quality and maturity bar. Give a one-line reason and stay warm.
- Park borderline or promising-but-premature submissions (for example, a young project that may later clear the star threshold) rather than closing hard.
Explaining quality concerns
State the concern plainly and briefly, point to the specific guideline, and where possible suggest the concrete fix. Keep the contributor's path back to acceptance clear.
Maintainer judgement
Produce a recommendation and, if helpful, the concrete edit. Leave the actual merge or close to the human maintainer. When unsure, flag it rather than deciding.
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 · 43 lines · 403 tokens per session scan A 14e0c12fb7c2
Awesome-Prompt-Engineering contribution-review.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 403 tokens to every session, about $0.0016 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.