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/chefallan/awesome-context-engine/agents-mdgit clone --depth 1 https://github.com/chefallan/awesome-context-engineWhat 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 | $0.00196 | $0.00196 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
awesome-context-engine AGENTS.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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- awesome-context-engine CLAUDE.md — 97% identical, 2 lines differ
What it actually says
Agent Rules
- Read .awesome-context/ai-context.md first.
- Use .awesome-context/project-map.md for repo structure.
- Use .awesome-context/workflows.md and .awesome-context/skills/ for repeatable tasks.
- Preserve preferences from .awesome-context/preferences.md.
- After completing tasks, suggest updates to .awesome-context/memory.md.
- Never store secrets, tokens, credentials, or private keys in memory files.
awesome-context-engine Integration
- Read .awesome-context/ai-context.md first.
- Use .awesome-context/project-map.md and .awesome-context/workflows.md.
- Preserve preferences from .awesome-context/preferences.md.
- After each completed prompt result that changed files, run awesome-context-engine sync to refresh context.
- Suggest updates to .awesome-context/memory.md after meaningful changes.
- Never store secrets, tokens, credentials, or private keys in memory files.
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.
- 2d ago First seen · 21 lines · 196 tokens per session scan A b8bf62fb768b
awesome-context-engine AGENTS.md is an instructions file published in the GitHub repository chefallan/awesome-context-engine (2 stars, last pushed 4mo ago), licensed MIT. It adds 196 tokens to every session, about $0.0010 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
memorix CLAUDE.md
Instructions for AVIDS2/memorix, covering memorix - agent instructions for claude code, using memorix memory tools, when to search memory, when to store memory and when to resolve memory.
DevoxxGenieIDEAPlugin GEMINI.md
Instructions for devoxx/DevoxxGenieIDEAPlugin, a project described as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your project code. Latest version now also supports Spec Driven Development…
rosetta AGENTS.md
Instructions for griddynamics/rosetta: Main goal: cover E2E AI PDLC engineering workflows at foundation level for AI-First SDLC in enterprise. Top-level or orchestrator agents MUST READ docs/ARCHITECTURE.md contains technical details and guidance, and docs/CONTEXT.md - business context. Subagents - when needed.…
Context-Engine GEMINI.md
Instructions for Context-Engine-AI/Context-Engine, covering ai agent rules for context-engine mcp tools, stop — read this first, glossary, tool selection decision tree and requirements.
apex-accelerator instructions.instructions.md
Guidelines for creating high-quality custom instruction files for GitHub Copilot.
smart-tree CLAUDE.md
Instructions for 8b-is/smart-tree, covering claude.md, project overview, build & development commands, architecture and cli → daemon flow.