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-agentic-engineering/repository-maintenancegit 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/repository-maintenance)<a href="https://agentmods.dev/instructions/natnew/awesome-agentic-engineering/repository-maintenance"><img src="https://agentmods.dev/badge/instructions/natnew/awesome-agentic-engineering/repository-maintenance.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.1 | $0.00271 | $0.00271 |
| Opus 5 | $0.00135 | $0.00135 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
Awesome-Agentic-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 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.
What it actually says
Repository maintenance
Guidance for maintenance-only changes to Markdown across the repository.
These instructions are for maintenance-only Markdown edits. When a task involves adding, removing, reviewing, scoring or repositioning an awesome-list entry — or restructuring README sections — follow readme-curation.instructions.md and link-and-source-quality.instructions.md instead. Do not use this file to judge entry quality or replace those more specific instructions.
- Keep edits minimal and reversible. Prefer the smallest change that fixes the problem.
- Avoid unnecessary rewrites. Do not reword or restructure content that is already clear and correct.
- Preserve the maintainer's concise, engineering-led voice and the existing tone of each document.
- Do not introduce large structural changes — new sections, reordering, or renamed headings — unless they have been explicitly requested.
- Keep Markdown readable and consistent: match the surrounding heading levels, list styles, and table layouts.
- Do not hand-edit generated site output under
docs/orassets/github/; it is regenerated by the publish workflow. - For substantive content changes, add a one-line bullet under
## [Unreleased]inCHANGELOG.md. Do not add changelog entries for typo-only, formatting-only, or link-normalisation fixes unless 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.
- 5d ago First seen · 18 lines · 271 tokens per session scan A dc2dcd947b1f
Awesome-Agentic-Engineering repository-maintenance.instructions.md is an instructions file published in the GitHub repository natnew/Awesome-Agentic-Engineering (4 stars, last pushed 11d ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 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-31.
Other instructions, from other repositories
Awesome-Prompt-Engineering AGENTS.md
Instructions for natnew/Awesome-Prompt-Engineering, covering agents.md, repository north star, agent role, trust boundary and read order.
Awesome-Prompt-Engineering CLAUDE.md
Instructions for natnew/Awesome-Prompt-Engineering, covering claude.md, north star, claude's role, claude behaviour rule and always-loaded context.
Awesome-Prompt-Engineering copilot-instructions.md
Instructions for natnew/Awesome-Prompt-Engineering, covering github copilot instructions, about this repository, how to treat the repository, contribution standard and reviewing suggested additions.
Awesome-Prompt-Engineering contribution-review.instructions.md
Instructions for natnew/Awesome-Prompt-Engineering, covering reviewing pull requests and issues, tone, how to respond, explaining quality concerns and maintainer judgement.
Awesome-Prompt-Engineering readme-curation.instructions.md
Instructions for natnew/Awesome-Prompt-Engineering, covering curating the main list (readme.md), structure and ordering, descriptions, links and before adding.
Awesome-Prompt-Engineering repository-maintenance.instructions.md
Instructions for natnew/Awesome-Prompt-Engineering, covering maintenance edits across markdown files, keep changes minimal, preserve voice and structure, no large or structural changes without direction and readability.