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/timurgaleev/memex/claude-mdgit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/claude-md)<a href="https://agentmods.dev/instructions/timurgaleev/memex/claude-md"><img src="https://agentmods.dev/badge/instructions/timurgaleev/memex/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 | $0.03448 | $0.03448 |
| Opus 5 | $0.01724 | $0.01724 |
| Sonnet 5 | $0.00690 | $0.00690 |
| Haiku 4.5 | $0.00345 | $0.00345 |
Grade B, and why
memex 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- For new timer units: `sudo systemctl start <unit>` succeeds, then `systemctl is-active` reports OK How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Rules for AI agents working in this repo
This file is auto-loaded by Claude Code (and other AI coding agents that honor the convention). It defines the safety and scope rules every agent must follow when editing this codebase.
What you are allowed to do
- Read files and understand the codebase.
- Edit config, scripts, and docs when explicitly asked.
- Run
terraform planandmake auditto show what would change. - Run AWS CLI read-only commands (
describe,list,get). - Commit and push ONLY when explicitly asked.
What you are NOT allowed to do without explicit confirmation
Destructive infrastructure changes
- NEVER run
terraform applywithout showing the plan first AND getting explicit "yes, apply". - NEVER destroy or replace running EC2 instances without explicit confirmation.
- NEVER change availability zones, instance types, or subnet configurations without warning.
- If a terraform plan shows ANY resource being destroyed or replaced — STOP and ask first.
File and git operations
- NEVER run
git reset --hardor any destructive git command. - NEVER commit files that were not explicitly included in the request.
- NEVER stage and commit deleted files unless explicitly asked to remove them.
- Disk files and git files are DIFFERENT — do not confuse them.
Scope of work
- Do ONLY what was asked. If asked to fix a config file, fix that file only.
- Do NOT remove integrations, features, or code that was not mentioned.
- Do NOT "clean up" things that look unused — ask first.
- Do NOT add, remove, or modify terraform resources beyond what was asked.
- Do NOT add monitoring, alarms, notifications, health checks, dashboards, or any new AWS infrastructure that the user did not explicitly request, even if it would "improve reliability" or "catch the next failure". Discuss the idea in plain text first, agree on the approach, and only then build.
Key principle
Ask before acting on anything irreversible. The cost of one confirmation message is zero. The cost of a destroyed EC2 instance or lost disk data is high.
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.
- today Changed · +7 lines · +149 tokens per session 3f59bc588c75
- 4d ago First seen · 254 lines · 3,299 tokens per session scan B 374219a83933
memex CLAUDE.md is an instructions file published in the GitHub repository timurgaleev/memex (8 stars, last pushed 2d ago), licensed MIT. It adds 3,448 tokens to every session, about $0.0172 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
obsidian-mcp-server AGENTS.md
Instructions for cyanheads/obsidian-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — obsidianlisttags.
nutrition-mcp CLAUDE.md
Claude Code instructions for akutishevsky/nutrition-mcp, covering claude.md, project overview, deploying, publishing to the registry and commands.
data-olympus AGENTS.md
Instructions for knaisoma/data-olympus, covering data olympus, project overview, architecture, development workflow and code standards.
grounded-knowledge-engine AGENTS.md
Instructions for dimosgit/grounded-knowledge-engine, covering agent guide, agent operating contract, authorship and attribution, two npm trees and commands — engine (repo root).
AgenticMind AGENTS.md
Instructions for Moai-Team-LLC/AgenticMind, covering agents.md, what this is, it implements a standard — read it first, commands and conventions (please honor).
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.