What is memex AGENTS.md?

Repository-specific instructions for AI agents working on Memex, a service accessed through the Model Context Protocol. They describe the required workflow for changes, testing, deployment, and self-review.

Use them when changing Memex code, documentation, infrastructure, or deployment configuration.

They prevent agents from skipping project rules such as reading the required documentation, using tests where appropriate, and confirming risky operations.

How timurgaleev/memex configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to timurgaleev/memex. 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/timurgaleev/memex/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/timurgaleev/memex

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/timurgaleev/memex/agents-md/github.svg)](https://agentmods.dev/instructions/timurgaleev/memex/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/timurgaleev/memex/agents-md"><img src="https://agentmods.dev/badge/instructions/timurgaleev/memex/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/timurgaleev/memex/agents-md"><img src="https://agentmods.dev/badge/instructions/timurgaleev/memex/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,429 This file is loaded in full into every session.

When invoked 2,429 The same file — it is already loaded in full.

Security scan B 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.02429	$0.02429
Opus 5.5	$0.00972	$0.00972
Sonnet 5.5	$0.00486	$0.00486
Haiku 4.5	$0.00243	$0.00243

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

Security

Grade B, and why

memex AGENTS.md scanned grade B with 2 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

| wget -qO- --post-file=/dev/stdin --header=Content-Type:application/json http://127.0.0.1:18790/mcp

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| wget -qO- --post-file=/dev/stdin --header=Content-Type:application/json http://127.0.0.1:18790/mcp

AGENTS.md · 174 lines

How it starts

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

AGENTS.md — Working in this Repo as an AI Agent

Companion to llms.txt (which is the doc map). This file is how to work: build, test, deploy, commit. Read CLAUDE.md first — it carries the user's irrevocable rules.

TL;DR

Always confirm before destructive ops (commit, terraform apply, EC2 recreate).
TDD where the logic is testable; smoke-test where the network is the test.
Containers run on a single EC2; deploy = git pull && docker compose up -d --build over SSM.
memex's brain index is rebuildable from source content; if RDS is wiped, re-sweep restores it (~5-10 min, $0 — Titan is credit-eligible).
memex is reached over MCP only (POST /mcp, through cloudflared or — with ingress_mode = "caddy" — a Caddy sidecar on the instance's own IP). No chat surface, no bot — just MCP clients (Claude Code, Codex, claude.ai, ChatGPT, …).
Callers authenticate with a personal access token bound to a source (memex auth create <name> --source <src>) or an OAuth client (memex auth register-client, enrollment mode for a shared team connector). The static public bearer is permanent, tenant-less and read-limited. Guides: docs/clients/.

Required workflow — run the skill for every change

No change is "done" until the skills have run. For every change — features, fixes, refactors, docs, infra — in order:

Self-review skill/agent. Dispatch the review agent whose specialty matches what you changed (the table in CLAUDE.md → "Self-review after each implementation"): security-engineer for auth / secrets / ingress, code-reviewer for logic / refactor, quality-guard for new tests, devops-automator for CI / docker / terraform, ai-engineer for engine / MCP / retrieval, reality-checker for "it's live now" claims, bug-hunter for adversarial sweeps, technical-writer for docs. Act on every CRITICAL / HIGH finding before declaring done.
Ship workflow. Follow CLAUDE.md → "Ship workflow": test → push → deploy → verify → release, in that order, every time. A change is not shipped until the live EC2 is running it and /health + the MCP smoke-test pass; user-facing version bumps end with a SemVer tag + GitHub release (see "Release" below).

Read the full file on GitHub · 174 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.

1mo ago Changed · +1 lines · +16 tokens per session a5e31490a3a2
1mo ago Changed · +100 tokens per session a253a6c92a1a
2mo ago First seen · 173 lines · 2,313 tokens per session scan B eb6c245176b9

Subscribe to this mod's changes

memex AGENTS.md is an instructions file published in the GitHub repository timurgaleev/memex (11 stars, last pushed 1mo ago), licensed MIT. It adds 2,429 tokens to every session, about $0.0097 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

bun mcp model-context-protocol pgvector second-brain self-hosted

memex AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memex AGENTS.mdtimurgaleev/memex	Instructions file	11	1mo ago	MIT	B	2,429	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

memex: Instructions file for Codex