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/vuau/agent-memory/agents-mdgit clone --depth 1 https://github.com/vuau/agent-memoryWhat 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.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
agent-memory 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 yesterday.
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@vuau/agent-memory - AGENTS
Router file for coding agents.
Note: This file is automatically managed by
@vuau/agent-memory. Do not add project-specific rules here, as they may be overwritten byagent-memory update.👉 For project-specific rules, context, and document mapping, see
.agents/CUSTOM.md
Priority
- User request first.
- The rules in
.agents/CUSTOM.md. - This
AGENTS.md. - Spec files in
.agents/spec/. - If conflict remains, choose smallest safe change and state assumption.
Memory Protocol
Session Start
- Read
.agents/MEMORY.mdbefore starting any task.
When to write
- User approves a decision or pattern → append to
.agents/MEMORY.md - Explore codebase/architecture → update relevant
.agents/spec/*.md - Start/finish a large task → update
.agents/TASKS.md
MEMORY.md entry format
- YYYY-MM-DD: <1-line decision or pattern> → detail
Place under the appropriate category. Add → detail pointer when full context exists in MEMORY-DETAIL.md.
TASKS.md update
Before ending a session with unfinished work, move items to ## In Progress or ## Up Next.
Rules
- Keep
MEMORY.mdentries to 1 line each. Details go in spec files. - If
MEMORY.md> 150 lines, archive old entries. - Do not create additional memory files outside
.agents/.
Coding Principles
- State assumptions before implementing. If ambiguous, ask — don't pick silently.
- Surgical changes: touch only what's needed, match existing style.
- Remove only dead code YOUR changes created. Mention pre-existing issues, don't fix.
- Every changed line must trace to user's request.
- Complex tasks: define success criteria, verify before done.
- Full details:
.agents/spec/coding-principles.md
Response Style
- Concrete, implementation-focused, caveman style (minimum words, zero fluff).
- Propose the simplest solution first (KISS & YAGNI) before writing code.
- If uncertain, say
I don't know, then give fastest verification step. - Do not invent files, APIs, or command outputs.
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.
- yesterday First seen · 54 lines · 486 tokens per session scan A de30b899d8ac
agent-memory AGENTS.md is an instructions file published in the GitHub repository vuau/agent-memory (2 stars, last pushed 2mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.