Borrowing it
Nothing to install: this file belongs to Goldentrii/AgentRecall-X. 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/Goldentrii/AgentRecall-X/main/AGENTS.mdgit clone --depth 1 https://github.com/Goldentrii/AgentRecall-XWrote 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/goldentrii/agentrecall-x/agents-md)<a href="https://agentmods.dev/instructions/goldentrii/agentrecall-x/agents-md"><img src="https://agentmods.dev/badge/instructions/goldentrii/agentrecall-x/agents-md.svg" alt="Measured on agentmods" 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.02047 | $0.02047 |
| Opus 5 | $0.01024 | $0.01024 |
| Sonnet 5 | $0.00409 | $0.00409 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
AgentRecall-X 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 7d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentRecall — Codex Agent Instructions
AgentRecall gives you persistent memory across sessions. The only thing the human ever does is describe intent — loading and saving memory is invisible runtime machinery that YOU, the agent, must drive without being asked.
This host (Codex, Cursor, or any raw MCP client) has no lifecycle hooks. Claude Code auto-fires memory at session start/stop via hooks; here there is no such hook. That means: if you don't call these tools yourself, nothing loads and nothing saves — silently. This is non-negotiable, not a nice-to-have:
- ENTRY — ALWAYS, every session, not just on trigger phrases. The moment a session resumes prior work, call
session_startFIRST, before acting on anything else. Do not wait for the user to say "load my context" — that phrase (see trigger table below) is an additional signal, not the only permitted trigger. - EXIT — ALWAYS, before you stop. Before ending a turn/session where you did meaningful work, call
session_endwith a real summary. Do not wait for the user to say "save this" — that phrase is an additional durable-intent trigger, not a gate you wait behind. Saying it is not saving it: only the tool call saves it. - DURABLE INTENT — call immediately, don't defer. The moment you or the user says save / remember / checkpoint / 记住 / 保存, call
session_end(orrememberfor a single fact) right then, not at some later "natural" stopping point. recallandcheckare safe to call freely, any time, with no gating at all.
Tool surface (verified against packages/mcp-server/src/index.ts + tool-surface-purity.test.mjs)
AgentRecall's real MCP surface is 5 tools by default, 6 with --full, 13 with AR_EXTRAS=1 --full — not the 10-tool list this file used to describe. That old list mixed in four project-board/status and bootstrap-scan/import tools that were deleted from the MCP surface on 2026-07-05 (zero organic MCP use); their logic lives on in the CLI only, see the CLI-equivalents table below.
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.
- 7d ago First seen · 131 lines · 2,047 tokens per session scan A a8bb4e07d6b8
AgentRecall-X AGENTS.md is an instructions file published in the GitHub repository Goldentrii/AgentRecall-X (371 stars, last pushed 6d ago), licensed MIT. It adds 2,047 tokens to every session, about $0.0102 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-30.
Other instructions, from other repositories
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).
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.
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).
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.