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/repository-maintenance.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/repository-maintenance)<a href="https://agentmods.dev/instructions/natnew/awesome-prompt-engineering/repository-maintenance"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/repository-maintenance/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/repository-maintenance"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-prompt-engineering/repository-maintenance.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.00368 | $0.00368 |
| Opus 5 | $0.00184 | $0.00184 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
Awesome-Prompt-Engineering repository-maintenance.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 9d 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
Maintenance edits across Markdown files
These rules apply to general upkeep of the Markdown content (fixing typos, clarifying wording, updating links, small consistency fixes).
This file is for small maintenance edits only. It is not for judging whether a new awesome-list entry should be accepted, deciding list-entry quality, changing README categories, or restructuring the list, and it does not replace the more specific README curation or link/source quality instructions. When a task involves adding, removing, reviewing, or repositioning an awesome-list entry, follow those more specific instructions instead.
Keep changes minimal
- Make the smallest edit that achieves the goal. Touch only what the task needs.
- Do not rewrite, reflow, or reorder content that is otherwise fine.
- Do not reformat existing content solely to satisfy lint rules that are
deliberately disabled in
.markdownlint-cli2.jsonc.
Preserve voice and structure
- Match the surrounding style, heading levels, and list conventions.
- Keep the maintainer's tone. Do not impose a different register or restructure sections.
- Internal links between pages point to the rendered
.htmlpaths (Jekyll + just-the-docs); keep that convention.
No large or structural changes without direction
- Do not add or remove sections, categories, or pages unless the maintainer asks.
- Do not change theme machinery (
_config.yaml,_layouts/,_includes/) or configuration files unless the task is explicitly about site rendering. - Treat badges, announcements, and contributor tables as protected.
Readability
- Keep Markdown clean and consistent: language identifiers on code blocks,
descriptive
alttext on images, and descriptive link text.
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.
- 9d ago First seen · 43 lines · 368 tokens per session scan A 8c9134ff0d95
Awesome-Prompt-Engineering repository-maintenance.instructions.md is an instructions file published in the GitHub repository natnew/Awesome-Prompt-Engineering (109 stars, last pushed 1mo ago), licensed MIT. It adds 368 tokens to every session, about $0.0018 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
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.
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.
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).
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).
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.
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.