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/copilot-instructionsgit 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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
awesome-context-engine copilot-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 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
awesome-context-engine Integration
- Read
.awesome-context/ai-context.mdfirst — it is the repo brain (rules, memory, module index, workflows). - For the full module catalog and architecture map, read
.awesome-context/repo-brain.md. - Use
.awesome-context/project-map.mdand.awesome-context/workflows.md. - Preserve preferences from
.awesome-context/preferences.md. - After each completed prompt result that changed files, run
ace syncto refresh context. - Suggest updates to
.awesome-context/memory.mdafter meaningful changes. - Never store secrets, tokens, credentials, or private keys in memory files.
When to fire ACE commands
| Situation | Command |
|---|---|
| Starting work on a file | ace context:pack <file> |
| Finished making changes | ace sync |
| User says remember/note/keep in mind | ace genesis capture --note "<lesson>" |
| User asks what was decided / do you remember | ace genesis recall "<topic>" |
| User asks impact of changing a file | ace context:impact <file> |
| User adds a rule or preference | ace memory add "<content>" |
| Fresh session, no context loaded | ace context:pack <entry-file> |
| Your draft violates a stored rule or preference | Revise before sending; then ace genesis capture --note "<lesson>" |
Never run ace auto — it is a RAM-heavy background watcher, not for agent use.
Self-Healing Protocol
This runs automatically — no commands needed. Before sending every response:
- Re-read the
## Persistent Memorysection of.awesome-context/ai-context.md(already loaded in your context). - Check your draft against every
[rule]and[warning]item. - If any rule is violated — silently revise your draft before sending. Do not mention the check unless the user asks.
Copilot Instructions
- 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.
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 · 46 lines · 517 tokens per session scan A a2eb126450b9
awesome-context-engine copilot-instructions.md is an instructions file published in the GitHub repository chefallan/awesome-context-engine (2 stars, last pushed 4mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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
agentlens CLAUDE.md
Instructions for RogerReed/agentlens, covering agentlens mcp and recurring maintenance tasks.
ctxmem AGENTS.md
Instructions for DoppiaG93/ctxmem: This repo has a ctxmem memory: a shared, git-committed record of decisions and code context. Treat it as your first source of truth and keep it correct. Follow this loop on EVERY request, without being asked.
brainstack copilot-instructions.md
Instructions for Hrithik-Gavankar/brainstack, covering brainstack context, career context, full skills inventory, workspace layout and engineering profile.
codemap CLAUDE.md
Instructions for JordanCoin/codemap, covering 🛑 stop — run codemap before any task, repo root requirement (critical) and required usage.
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…
packmind packmind-frontend-error-management.instructions.md
Instructions for PackmindHub/packmind: A global error boundary is already configured at the root level (in root.tsx) that automatically catches all page crashes, 404s, and loader failures. This standard defines when and how to use explicit... .