agent-recall-trail: Instructions file for Codex

AGENTS.md

agent-recall-trail AGENTS.md is an instructions file for Codex, OpenCode from fantasyce/agent-recall-trail. It costs 202 tokens per session, scanned A, original, Apache-2.0.

Project instructions for Agent Recall Trail, a system for private agent memory and human-reviewed shared knowledge.

In plain words
What is it for?
Following the project’s test-driven development process, maintaining separate SQLite memory files, and avoiding unsafe data or unrelated configuration changes.
Why use it?
They give developers rules for testing, separating memory from published knowledge, protecting secrets, and keeping agent identities isolated.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is fantasyce/agent-recall-trail's own configuration. It tells Codex and OpenCode how to work on agent-recall-trail itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-recall-trail configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fantasyce/agent-recall-trail. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fantasyce/agent-recall-trail/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/fantasyce/agent-recall-trail

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for agent-recall-trail AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fantasyce/agent-recall-trail/agents-md/github.svg)](https://agentmods.dev/instructions/fantasyce/agent-recall-trail/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/fantasyce/agent-recall-trail/agents-md"><img src="https://agentmods.dev/badge/instructions/fantasyce/agent-recall-trail/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.

agentmods 80×15 button for agent-recall-trail AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fantasyce/agent-recall-trail/agents-md"><img src="https://agentmods.dev/badge/instructions/fantasyce/agent-recall-trail/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 202 This file is loaded in full into every session.
When invoked 202 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00202 $0.00202
Opus 5.5 $0.00081 $0.00081
Sonnet 5.5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured 1mo ago against content hash d374e9d94217, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-recall-trail 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.

AGENTS.md · 13 lines

What it actually says

ART development contract

  • The current design and implementation plans under docs/specs/ and docs/plans/ are the product and acceptance contracts.
  • Use test-driven development. Observe each new behavior test fail before implementing it.
  • Keep every Agent Vault in a physically distinct SQLite file and bind MCP identity at process start.
  • Memory and published knowledge are different object families. Agents cannot perform human governance. A bound Agent may perform distinctly labeled delegated governance only while the persistent local policy is enabled.
  • Do not read, copy, translate, or structurally imitate competitor source code, schemas, prompts, tests, names, or directory layouts.
  • Tests use an explicit task-owned ART_HOME; never write test data to the formal ~/.across runtime.
  • Do not modify unrelated products, existing knowledge sources, or formal Codex/DSH configuration during automated tests.
  • Do not persist secrets, full transcripts, unrestricted command output, or recalled bundle bodies.
Changes

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.

  1. 1mo ago Changed · +2 lines · +21 tokens per session d374e9d94217
  2. 1mo ago First seen · 11 lines · 181 tokens per session scan A 5383a1a9a5b9

Subscribe to this mod's changes

agent-recall-trail AGENTS.md is an instructions file published in the GitHub repository fantasyce/agent-recall-trail (0 stars, last pushed 28d ago), licensed Apache-2.0. It adds 202 tokens to every session, about $0.0008 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens