Borrowing it
Nothing to install: this file belongs to darland6/cory-mem. 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/darland6/cory-mem/main/CLAUDE.mdgit clone --depth 1 https://github.com/darland6/cory-memWrote 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/darland6/cory-mem/claude-md)<a href="https://agentmods.dev/instructions/darland6/cory-mem/claude-md"><img src="https://agentmods.dev/badge/instructions/darland6/cory-mem/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.01374 | $0.01374 |
| Opus 5 | $0.00687 | $0.00687 |
| Sonnet 5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
cory-mem CLAUDE.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 8d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cory-mem
Personal memory system for Claude-based AI projects with semantic search, session management, and MCP integration.
Architecture
src/cory_mem/
├── core/ # Memory orchestration
│ ├── memory_manager.py # Central orchestrator (sessions, inject, retrieve, search, sync)
│ ├── short_term.py # Session-scoped memory with TTL
│ ├── long_term.py # Persistent memory storage
│ └── lifecycle_tracker.py
├── models/ # Immutable dataclasses
│ ├── base.py # Memory, MemoryType, MemoryStatus
│ ├── personal.py # PersonalMemory, PersonalCategory
│ ├── knowledge.py # KnowledgeMemory, KnowledgeDomain
│ ├── interaction.py # InteractionMemory
│ └── project.py # ProjectMemory
├── search/ # Hybrid search (FAISS + keyword)
│ ├── engine.py # SearchEngine (semantic, keyword, hybrid)
│ └── keyword.py # TF-IDF keyword search
├── embeddings/ # Pluggable embedding providers
│ ├── base.py # EmbeddingProviderProtocol
│ ├── local.py # sentence-transformers (default)
│ ├── openai.py # OpenAI embeddings
│ └── claude.py # Anthropic embeddings
├── storage/ # Persistence layer
│ ├── json_storage.py # Atomic JSON files with fcntl locking
│ └── faiss_index.py # FAISS vector index
├── api/ # REST API
│ ├── main.py # FastAPI app
│ └── routers/ # memories, search, scheduler, versioning, analytics
└── mcp/ # MCP server
├── server.py # CoryMemServer
├── tools.py # MCP tool definitions
└── resources.py # MCP resource handlers
Memory Types
class MemoryType(str, Enum):
PERSONAL = "personal" # User preferences, facts, relationships
KNOWLEDGE = "knowledge" # Learned facts, skills, domain knowledge
INTERACTION = "interaction" # Conversation history, feedback
PROJECT = "project" # Project-specific context
GENERIC = "generic" # Catch-all
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.
- 8d ago First seen · 192 lines · 1,374 tokens per session scan A 53472903ce2d
cory-mem CLAUDE.md is an instructions file published in the GitHub repository darland6/cory-mem (1 stars, last pushed 7mo ago), licensed MIT. It adds 1,374 tokens to every session, about $0.0069 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
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.
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.