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/dowlings/librechat-mnemonic/agents-mdgit clone --depth 1 https://github.com/dowlings/librechat-mnemonicWrote 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/dowlings/librechat-mnemonic/agents-md)<a href="https://agentmods.dev/instructions/dowlings/librechat-mnemonic/agents-md"><img src="https://agentmods.dev/badge/instructions/dowlings/librechat-mnemonic/agents-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 | $0.00430 | $0.00430 |
| Opus 5 | $0.00215 | $0.00215 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
librechat-mnemonic 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 4d 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
Agent Guidelines
Workflow
- Read before writing. Understand the existing code, tests, and architecture before making changes. Start with
README.md, then the files relevant to the task. - Make focused changes. Do not reformat unrelated code, rename variables, or "improve" things outside the scope of the task.
- Add or update tests. Every behavioural change should have corresponding test coverage. Run
npm testbefore committing. - Run validation. Always run
npm testandnpm run typecheckbefore pushing. If either fails, fix the issue before committing. - Commit checkpoints. For longer tasks, commit and push coherent checkpoints rather than waiting until the end. Each commit should leave the codebase in a working state.
- Do not merge. Create or update a pull request targeting
main. Let a human review and merge.
Code Style
- Follow the existing patterns in the codebase. Do not introduce new dependencies without justification.
- Keep comments concise and explain why, not what.
- Use the existing logger (
pino) for all logging. Neverconsole.log. - Environment-driven configuration via
zodschemas. No config files.
Testing
- Tests use
vitest. Runnpm testfor the full suite. - Mock external dependencies (mnemonic, MongoDB, HTTP) — never hit real services in tests.
- Each test file should be self-contained with its own fixtures.
Architecture Notes
src/proxy/handler.ts— the request path; where memory recall and injection happen.src/memory/service.ts— the shared core for both the proxy and MCP endpoint.src/mnemonic/client.ts— the MCP client with read/write queue separation.src/cache.ts— TTL cache with hit/miss tracking.src/telemetry.ts— Langfuse telemetry (noop when credentials are missing).src/config.ts— all configuration, env-driven via zod.
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.
- 4d ago First seen · 32 lines · 430 tokens per session scan A 0004ed6a0f0f
librechat-mnemonic AGENTS.md is an instructions file published in the GitHub repository dowlings/librechat-mnemonic (0 stars, last pushed yesterday), licensed MIT. It adds 430 tokens to every session, about $0.0022 per session on Opus 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).
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.
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 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).
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.
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.