Borrowing it
Nothing to install: this file belongs to Tibu142/memorix. 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/Tibu142/memorix/main/CLAUDE.mdgit clone --depth 1 https://github.com/Tibu142/memorixWrote 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/tibu142/memorix/claude-md)<a href="https://agentmods.dev/instructions/tibu142/memorix/claude-md"><img src="https://agentmods.dev/badge/instructions/tibu142/memorix/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.00614 | $0.00614 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
memorix 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 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.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memorix — Agent Instructions for Claude Code
You have access to Memorix, a cross-agent memory system. Use it to persist and recall project knowledge across sessions.
When to SEARCH memory (memorix_search)
- Session start: Always search for recent context at the beginning of a conversation
- Before making decisions: Search for past decisions on the same topic
- When the user asks "remember"/"what did we"/"last time": Search for relevant history
- Before implementing features: Check if similar work was done before
- When encountering errors: Search for known gotchas and past solutions
When to STORE memory (memorix_store)
- Architecture decisions: Why you chose X over Y (type:
decision) - Bug fixes: Root cause and solution (type:
problem-solution) - Gotchas/pitfalls: Things that tripped you up (type:
gotcha) - How things work: Non-obvious system behavior (type:
how-it-works) - Changes made: Significant code changes (type:
what-changed) - Trade-offs: Compromises and their reasoning (type:
trade-off) - Session goals: What the user asked for at session start (type:
session-request)
When to check RETENTION (memorix_retention)
- Periodically check which memories are stale or candidates for archiving
- Review top-relevant memories to avoid duplicating past work
Best Practices
- Be specific in titles: "Fixed Docker timeout from 30s to 60s" not "Fixed bug"
- Include facts: Structured data like "Default port: 3001", "Retry count: 3"
- Tag files: Always include filesModified when you edit files
- Use concepts: Add searchable keywords for future retrieval
- Don't over-store: Only store knowledge that would be useful in a future session
- Entity naming: Use kebab-case descriptive names like "auth-module", "docker-config"
Tool Quick Reference
| Tool | When | Example |
|---|---|---|
memorix_search |
Find past knowledge | query: "authentication" |
memorix_store |
Save new knowledge | type: "decision", title: "Use JWT for auth" |
memorix_detail |
Get full observation | ids: [42, 43] |
memorix_timeline |
See what happened around an event | anchorId: 42 |
memorix_retention |
Check memory health | action: "summary" |
memorix_rules_sync |
Sync agent rules | action: "status" |
memorix_workspace_sync |
Migrate workspace configs | action: "scan" |
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 · 48 lines · 614 tokens per session scan A f1c3d2d309b1
memorix CLAUDE.md is an instructions file published in the GitHub repository Tibu142/memorix (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 614 tokens to every session, about $0.0031 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.