Borrowing it
Nothing to install: this file belongs to notsointresting/mnemex. 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/notsointresting/mnemex/main/AGENTS.mdgit clone --depth 1 https://github.com/notsointresting/mnemexWrote 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/notsointresting/mnemex/agents-md)<a href="https://agentmods.dev/instructions/notsointresting/mnemex/agents-md"><img src="https://agentmods.dev/badge/instructions/notsointresting/mnemex/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.
<a href="https://agentmods.dev/instructions/notsointresting/mnemex/agents-md"><img src="https://agentmods.dev/badge/instructions/notsointresting/mnemex/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00305 | $0.00305 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
mnemex 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 2mo 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.
What it actually says
mnemex — Agent Build Context
Sources of truth
Read implementation-plan-opus48.md, codebase-mind-improved-plan.md,
goal-command.md, and CLAUDE.md before changing the project. Build phases in plan
order; Phase 1's anchor core must be complete before any indexer work.
Goal
Build a local-first MCP server that anchors each remembered decision to a file/symbol and content hash, then delivers relevant context just in time. Use one SQLite file with sqlite-vec and FTS5, and distribute context through MCP, skills, hooks, and AGENTS.md.
Orchestration rules
- Give each subagent one bounded contract with inputs, outputs, and exact tests.
- Require diffs, test results, and a self-report; never blind-merge.
- A phase is complete only after its objective gate passes.
- Use a separate verifier instance; authors do not grade their own work.
- Keep changes within the current phase and do not add speculative APIs.
Hard constraints
- Core features stay local and require no cloud API or ML model.
- Context caps are hard limits: 800 tokens at session start and 400 for JIT.
- Support macOS, Linux, and Windows on Python 3.10–3.13.
- Strip secrets and PII at write time; the Phase 6 security gate is blocking.
- Prefer a pluggable structural backend over implementing another parser.
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.
- 2mo ago First seen · 27 lines · 305 tokens per session scan A ce18c75a73ee
mnemex AGENTS.md is an instructions file published in the GitHub repository notsointresting/mnemex (1 stars, last pushed 3mo ago), licensed MIT. It adds 305 tokens to every session, about $0.0012 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.
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.