Recall: Instructions file for Codex

AGENTS.md

Recall AGENTS.md is an instructions file for Codex, OpenCode from samzong/Recall. It costs 959 tokens per session, scanned A, original, MIT.

Repository instructions for Recall, a Rust command-line and terminal interface app that indexes AI coding sessions into a SQLite database for searching, usage tracking, and sharing. They explain the project's structure, boundaries, commands, and development rules.

In plain words
What is it for?
Use them when modifying Recall, especially its Rust workspace, session indexing, database, terminal interface, adapters, extensions, or website.
Why use it?
They give coding agents the local rules they need to change the repository safely and consistently.

Instructions file for CodexOpenCode

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

This is samzong/Recall's own configuration. It tells Codex and OpenCode how to work on Recall 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 Recall configures →

Reuse

Borrowing it

Nothing to install: this file belongs to samzong/Recall. 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/samzong/Recall/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/samzong/Recall

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 Recall AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/samzong/recall/agents-md"><img src="https://agentmods.dev/badge/instructions/samzong/recall/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 959 This file is loaded in full into every session.
When invoked 959 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.00959 $0.00959
Opus 5.5 $0.00384 $0.00384
Sonnet 5.5 $0.00192 $0.00192
Haiku 4.5 $0.00096 $0.00096

Measured 20d ago against content hash 9c1306b20efa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Recall 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 20d 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 · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Recall

Rust CLI/TUI for indexing and searching local AI coding sessions. Data flow: adapters -> sync -> SQLite -> search -> CLI/TUI.

Read the nested AGENTS.md before changing src/adapters/, src/db/, src/tui/, extensions/, or website/. CLAUDE.md links to this file; edit this file once.

Contributing

Repository owners, members, and collaborators are exempt. Everyone else, including agents acting for a contributor, follows these rules; .github/workflows/contribution-gate.yml checks them on every pull request.

  • Work only on an open issue assigned to you. Check assignees in gh issue view <issue>; to claim an unassigned issue, comment /assign and confirm you then appear in assignees. An assignment with no linked pull request after 15 days may be released.
  • Every pull request resolves an issue assigned to its author: put Closes #<issue> in the description.
  • A human opens the pull request and authors every commit, signing off with git commit -s using an email linked to their GitHub account. Bot or agent accounts must not open the pull request, author commits, or sign off.
  • The description has a ## Test evidence section: the tool and version, OS, what you ran against real data or a real installation, the Recall output you observed, and what you could not verify. Tests and make check alone do not count.
  • When the check fails, fix the cause, then edit the description or push to run it again.

Build and verify

  • make check is required before push and is the CI gate: dependency audit, format check, workspace Clippy with --all-targets --features bench, then workspace tests. Install the cargo-audit version pinned in .github/workflows/ci.yml.
  • make build builds core; cargo build -p recall-<name> builds an extension binary. cargo test <filter> runs focused core tests.
  • Core integration tests belong in src/integration/, enabled by src/lib.rs; tests/fixtures/ holds data. Do not add root tests/*.rs targets. Other workspace crates keep their own test layouts.
  • Website commands and checks are separate; see website/AGENTS.md.

Read the full file on GitHub · 76 lines

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. 20d ago Changed · +22 lines · +274 tokens per session 9c1306b20efa
  2. 27d ago Changed · -2 lines · -37 tokens per session fc1f5295dac0
  3. 1mo ago Changed · -75 lines · -1,141 tokens per session 6a46bb060cca
  4. 1mo ago Changed · +6 lines · +74 tokens per session 19df1947b982
  5. 1mo ago First seen · 125 lines · 1,789 tokens per session scan A 2822801a1a61

Subscribe to this mod's changes

Recall AGENTS.md is an instructions file published in the GitHub repository samzong/Recall (107 stars, last pushed 2d ago), licensed MIT. It adds 959 tokens to every session, about $0.0038 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-30.

Related

Other instructions, from other repositories