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/jyswee/agenticmemory/agents-mdgit clone --depth 1 https://github.com/jyswee/agenticmemoryWhat 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.00841 | $0.00841 |
| Opus 5 | $0.00420 | $0.00420 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
agenticmemory 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 87 lines · 841 tokens per session scan A b4b2f8631eda
agenticmemory AGENTS.md is an instructions file published in the GitHub repository jyswee/agenticmemory (1 stars, last pushed 1mo ago), with no licence file. It adds 841 tokens to every session, about $0.0042 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
PrismerCloud CLAUDE.md
Instructions for Prismer-AI/PrismerCloud, covering claude.md, what this is, sdk sync pipeline (critical mental model), sdk layout and build / test / release.
memex AGENTS.md
Instructions for iamtouchskyer/memex, covering memex — agent working instructions, what is this, before you touch anything, how the code is layered and files you'll actually need.
gomaa AGENTS.md
Instructions for M4F-S/gomaa, covering 🧠 gomaa autonomous agent ecosystem & vps operations guide, 🌐 production vps infrastructure, 🤖 the 5-agent hermes fleet (per-agent memory databases), ⚡ quick operations cli (./scripts/vps.sh) and 2. run runtime mcp health audit across all agents.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.
brain-os copilot-instructions.md
Instructions for brainOS-HQ/brain-os, covering github copilot instructions, read this first, critical rules (also in agents.md) and known bugs (v0.4.1 fixes pending).
brain-os CLAUDE.md
Instructions for brainOS-HQ/brain-os, covering claude.md, agent instructions, build / dev, publish flow and project memory.