Borrowing it
Nothing to install: this file belongs to wefio/NodeMemoryGraph. 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/wefio/NodeMemoryGraph/main/AGENTS.mdgit clone --depth 1 https://github.com/wefio/NodeMemoryGraphWrote 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/wefio/nodememorygraph/agents-md)<a href="https://agentmods.dev/instructions/wefio/nodememorygraph/agents-md"><img src="https://agentmods.dev/badge/instructions/wefio/nodememorygraph/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/wefio/nodememorygraph/agents-md"><img src="https://agentmods.dev/badge/instructions/wefio/nodememorygraph/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.00439 | $0.00439 |
| Opus 5.5 | $0.00176 | $0.00176 |
| Sonnet 5.5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
NodeMemoryGraph 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 1mo 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NMG Agent bootstrap
This entry owns the stable discovery protocol. Keep module inventories, commands, implementation status, and environment-specific setup at their current owners.
Find the context for the next action
- Search for the task's terms, symbols, or error text in a narrow relevant scope. Use the current directory tree and manifests to locate code; expand the search only when that scope does not answer the question.
- Read applicable instructions along the target path and the nearest relevant README. Find repository Skills by their names and descriptions; follow the development workflow before editing and the specialized workflow when its stated condition applies.
- Read the relevant contract section and the exact code or test involved. Keep its definitions, conditions, and exceptions together. Follow a reference when it supplies a missing definition, an affected dependency, or an applicable obligation; a background link alone is not a requirement to read another file.
- Stop expanding when the next action, its constraints, and its verification are clear. Reopen discovery when evidence conflicts or the task crosses a boundary.
Maintain shared knowledge
Use current code and owning documents to establish facts; experiments and past decisions supply evidence and rationale. Update the existing owner with a behavior change rather than adding another summary. Preserve unrelated working-tree edits.
Do not place necessary files in cache folders, including TEMP and tmp. Please follow Git best practices when using Git.
It is essential to write code that is readable, maintainable, and extensible. You
can employ appropriate design patterns to achieve this, but avoid using patterns
simply for the sake of using them. If a problem can be solved with a simple
if-else statement, there is no need to implement a combination of Strategy,
Factory, and Chain of Responsibility patterns. Cramming too many patterns into a
single class often results in over-engineering.
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.
- 1mo ago Changed · +10 lines · +120 tokens per session 97df92c3854a
- 1mo ago Changed · -17 lines · -353 tokens per session 2d4108da0500
- 1mo ago Changed · +5 lines · +88 tokens per session 13d0acc5048e
- 1mo ago Changed · +13 lines · +198 tokens per session f41a223c99c0
- 1mo ago Changed · +11 lines · +173 tokens per session 805ab6171479
- 2mo ago First seen · 19 lines · 213 tokens per session scan A 61227baf408d
NodeMemoryGraph AGENTS.md is an instructions file published in the GitHub repository wefio/NodeMemoryGraph (0 stars, last pushed today), licensed MIT. It adds 439 tokens to every session, about $0.0018 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.