Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/zszz3/agentrecall/claude-mdgit clone --depth 1 https://github.com/zszz3/AgentRecallWrote 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/zszz3/agentrecall/claude-md)<a href="https://agentmods.dev/instructions/zszz3/agentrecall/claude-md"><img src="https://agentmods.dev/badge/instructions/zszz3/agentrecall/claude-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.03373 | $0.03373 |
| Opus 5 | $0.01687 | $0.01687 |
| Sonnet 5 | $0.00675 | $0.00675 |
| Haiku 4.5 | $0.00337 | $0.00337 |
Grade B, and why
AgentRecall CLAUDE.md scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **`bin/*.cjs` are dependency-free CommonJS with no build output** (launcher, self-updater, statusline, session-sync and memory hooks, MCP setup). They must work straight out of a global npm install, are idempotent and How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Also read AGENTS.md — it holds the binding rules for release notes, dual-app changes, merge/versioning, and safe test practices. This file covers commands and architecture.
Commands
npm run setup # setup:v1 + setup:v2 (do this instead of npm install — see below)
npm run dev:v1 # or dev:v2
npm test # test:repo + test:v1 + test:v2
npm run typecheck # tsc --noEmit in both apps
npm run release-note:check # MUST pass before opening an MR
npm run package:smoke:all # build + tarball-install smoke for both apps, in parallel
Per-app work is faster scoped:
npm --prefix apps/main-2.0 test # vitest run && node --test scripts/*.test.mjs
cd apps/main-2.0 && npx vitest run src/core/postgres/schema.test.ts # single file
cd apps/main-2.0 && npx vitest run -t "reconciles the OpenViking" # single test by name
cd apps/main-1.0 && npx vitest # watch mode
npm run test:workflow-transaction # V2 workflow-v2 / workspace-transaction gate
npm run test:workflow-performance # V2 incremental-IPC regression gate
Notes:
npm installalone is not enough.scripts/setup-app.mjsrunsnpm ciwithAGENT_RECALL_SKIP_STATUSLINE_INSTALL=1(so postinstall does not write into your real~/.claude), restores the embedded-PostgreSQL native symlinks that npm packing drops (V2 only), and validates the Electron binary. On Windows, the firstnpm run setup:v2needs an Administrator terminal for those symlinks.- There is no ESLint/Prettier/Biome/editorconfig.
tsc --noEmitis the only static gate; match surrounding style by hand. - CI (
.github/workflows/quality-check.yml) runs on ubuntu/macos/windows:setup→release-notes check-range→ fullnpm test(Linux only) ortest:scripts(mac/Windows) →package:smoke:all. The full suite is not green on Windows (POSIX paths, symlinks, fake-CLI spawning) — that is why mac/Windows only run the script tests.
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.
- 6d ago First seen · 100 lines · 3,373 tokens per session scan B 44990f3aa674
AgentRecall CLAUDE.md is an instructions file published in the GitHub repository zszz3/AgentRecall (762 stars, last pushed yesterday), licensed MIT. It adds 3,373 tokens to every session, about $0.0169 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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).
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.
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).