Borrowing it
Nothing to install: this file belongs to bobaba76/Engram. 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/bobaba76/Engram/main/AGENTS.mdgit clone --depth 1 https://github.com/bobaba76/EngramWrote 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/bobaba76/engram/agents-md)<a href="https://agentmods.dev/instructions/bobaba76/engram/agents-md"><img src="https://agentmods.dev/badge/instructions/bobaba76/engram/agents-md/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/bobaba76/engram/agents-md"><img src="https://agentmods.dev/badge/instructions/bobaba76/engram/agents-md.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.00736 | $0.00736 |
| Opus 5.5 | $0.00294 | $0.00294 |
| Sonnet 5.5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
Engram 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 2mo 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.
coder MCP - Primary Code Intelligence
This project uses coder MCP as the primary code-intelligence layer for codebase discovery, symbol lookup, dependency tracing, impact review, test discovery, and implementation context.
Prefer coder MCP for this repository. Use other code-intelligence tools only as optional fallbacks or secondary cross-checks when coder MCP cannot answer a question clearly.
Always Do
- Use coder MCP first when you need to locate files, symbols, routes, tests, dependencies, execution context, or likely implementation areas.
- Use
coder_semantic_code_searchorcoder_investigate_codebasewhen exploring unfamiliar features or trying to find the authoritative implementation. - Use
coder_resolve_targetandcoder_unified_contextwhen you need focused symbol-level context (callers, callees, deps, neighborhood in one call). - Before modifying a function, class, method, route handler, shared module, public header, API contract, or embedded firmware boundary, use coder MCP to inspect symbol context, callers/callees, dependencies, or change impact as appropriate.
- Use
coder_find_tests_for_targetbefore or after implementation to identify relevant tests. - Use
coder_detect_changes,coder_change_impact_report, orcoder_post_change_reviewto review changed files, likely affected behavior, and test scope when preparing a commit or handoff. - For C/C++/embedded projects, use
coder_get_dependencies,coder_unified_context, andcoder_detect_changesto inspect header fan-in, call relationships, project/build files, startup/ISR/trap files, and peripheral/init/flash modules. - If coder MCP reports stale, incomplete, or low-confidence results, use normal file search/read tools or another code-intelligence system as a fallback.
Never Do
- NEVER skip reviewing callers, dependencies, or likely test scope for changes to shared or high-risk code.
- NEVER commit or hand off changes without reviewing local change scope using coder MCP or equivalent git diff inspection.
- NEVER ignore low-confidence C/C++ results when compiler/build context is missing. Treat them as useful guidance, then verify with source and build knowledge.
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.
- 2mo ago First seen · 46 lines · 736 tokens per session scan A afdceb183bf7
Engram AGENTS.md is an instructions file published in the GitHub repository bobaba76/Engram (5 stars, last pushed 2mo ago), licensed MIT. It adds 736 tokens to every session, about $0.0029 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.