Borrowing it
Nothing to install: this file belongs to natnew/Awesome-Agentic-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-Agentic-Engineering/main/.github/instructions/contribution-review.instructions.mdgit clone --depth 1 https://github.com/natnew/Awesome-Agentic-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-agentic-engineering/contribution-review)<a href="https://agentmods.dev/instructions/natnew/awesome-agentic-engineering/contribution-review"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-agentic-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-agentic-engineering/contribution-review"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-agentic-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.00414 | $0.00414 |
| Opus 5.5 | $0.00166 | $0.00166 |
| Sonnet 5.5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
Awesome-Agentic-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
Contribution and review
Guidance for reviewing pull requests and issues, and for editing the contribution process itself.
Tone
- Be warm, concise, and respectful. Thank the contributor and keep the project welcoming.
- Gate on the rubric, never on tone. Give a clear reason tied to a specific rubric dimension or policy line, and link the relevant doc (
CONTRIBUTING.md,RUBRIC.md, orANTI-PATTERNS.md). - Do not over-explain or over-apologise, and do not dilute a firm curation decision.
Reviewing a submission
- Read the cited evidence first. If sources are missing, request them before scoring.
- Score the seven dimensions in
RUBRIC.mdand check the three hard gates (Reliability, Evidence, Agentic relevance). - Check section placement, duplicates (
README.mdandappendix/), link resolution, and formatting.
Deciding
- Accept good-faith contributions that clear the hard gates, reach a total ≥ 27 / 45, resolve their links, and match the surrounding formatting.
- Fix small things yourself rather than bouncing them back: typos, column alignment, link normalisation, neutralising promotional wording, or a missing evidence tag you can verify.
- Request changes only when there is a substantive evidence, uniqueness, or scope gap. Name the specific dimension and what would clear it.
- Close politely clear anti-patterns, out-of-scope submissions, or duplicates with no added judgement. Point to
CONTRIBUTING.mdor the relevantANTI-PATTERNS.mditem.
Editing the contribution process
When changing CONTRIBUTING.md or the templates, keep edits minimal and preserve the existing rubric, merge threshold, evidence tags, and review flow unless the change has been explicitly requested.
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 · 31 lines · 414 tokens per session scan A 445581ee7d31
Awesome-Agentic-Engineering contribution-review.instructions.md is an instructions file published in the GitHub repository natnew/Awesome-Agentic-Engineering (4 stars, last pushed 7d ago), licensed MIT. It adds 414 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-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).
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.