Borrowing it
Nothing to install: this file belongs to pomazanbohdan/memory-mcp-1file. 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/pomazanbohdan/memory-mcp-1file/master/AGENTS.mdgit clone --depth 1 https://github.com/pomazanbohdan/memory-mcp-1fileWrote 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/pomazanbohdan/memory-mcp-1file/agents-md)<a href="https://agentmods.dev/instructions/pomazanbohdan/memory-mcp-1file/agents-md"><img src="https://agentmods.dev/badge/instructions/pomazanbohdan/memory-mcp-1file/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/pomazanbohdan/memory-mcp-1file/agents-md"><img src="https://agentmods.dev/badge/instructions/pomazanbohdan/memory-mcp-1file/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.07991 | $0.07991 |
| Opus 5 | $0.03995 | $0.03995 |
| Sonnet 5 | $0.01598 | $0.01598 |
| Haiku 4.5 | $0.00799 | $0.00799 |
Grade A, and why
memory-mcp-1file 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 834 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 AGENTS.md — AI Agent Master Protocol (MCP + VIDA Thinking)
⛔ L0 INVARIANTS (Never violate under any circumstance)
- [MUST] After ANY context compression/clearing, your FIRST action must be to read
AGENTS.md. - [MUST NOT] Never perform auto-commits without explicit user permission.
- [MUST NOT] Never propose or implement "hotfixes". Demand root-cause solutions.
- [MUST NOT] Never delete files or code blocks without explicit discussion.
- [MUST] Always use
/vida-thinkfor architectural decisions, debugging, or complex refactoring.
🔄 POST-COMPRESSION BOOT SEQUENCE (⛔ CRITICAL BLOCKER — NO EXCEPTIONS)
⛔ THIS IS A HARD STOP. DO NOT RESPOND TO THE USER, DO NOT CONTINUE ANY TASK, DO NOT ANSWER ANY QUESTION UNTIL ALL STEPS BELOW ARE FULLY EXECUTED WITH Read TOOL CALLS.
When context is compressed or cleared, you MUST execute this sequence before ANY other action. Violation = immediate protocol failure. No shortcuts. No "I already know". No skipping.
- Read
AGENTS.md— this file (full, not partial). Re-internalize all L0 invariants and protocols. - Read all
/vida-thinkalgorithm files — required for architectural decisions:_vida/algorithms/meta-analysis.md_vida/algorithms/pr-cot.md_vida/algorithms/mar.md_vida/algorithms/5-solutions.md_vida/shared/reasoning-modules.md
- Read
_vida/shared/beads-protocol.md— state management protocol. - Read the context summary — if one exists in the compressed context, use it to orient.
- Do NOT continue work until steps 1-3 are complete.
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.
- 9d ago First seen · 834 lines · 7,991 tokens per session scan A 4f9e594cdd2e
memory-mcp-1file AGENTS.md is an instructions file published in the GitHub repository pomazanbohdan/memory-mcp-1file (24 stars, last pushed 3mo ago), licensed MIT. It adds 7,991 tokens to every session, about $0.0400 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-30.
Other instructions, from other repositories
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.
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).
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.