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/yiliqi78/memory-work/claude-mdgit clone --depth 1 https://github.com/yiliqi78/memory-workWrote 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/yiliqi78/memory-work/claude-md)<a href="https://agentmods.dev/instructions/yiliqi78/memory-work/claude-md"><img src="https://agentmods.dev/badge/instructions/yiliqi78/memory-work/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.04330 | $0.04330 |
| Opus 5 | $0.02165 | $0.02165 |
| Sonnet 5 | $0.00866 | $0.00866 |
| Haiku 4.5 | $0.00433 | $0.00433 |
Grade A, and why
memory-work 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 5d 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Personal Agent System Entry Point. Auto-injected by Cowork each session.
Language Rules
- Internal thinking always uses your preferred language (configured in USER.md)
- User conversations default to your language choice, unless you switch mid-session
- Code comments, commit messages use English unless otherwise specified
- Documentation files follow your project's style guide
System Boot Sequence
Trigger Words
When you send one of these trigger phrases, execute the full boot sequence:
boot/start work/initialize(or equivalent in your language)
First-Run Detection
Check Step (always first):
- Attempt to read
USER.md - Scan for template placeholders (e.g.,
[Your Name],[Your Project],TBD) - If placeholders found → Run INITIALIZATION FLOW (below)
- If placeholders absent → Run NORMAL STARTUP SEQUENCE (below)
Initialization Flow (First-Time Users)
Execute only if first-run detection confirms template placeholders in USER.md.
Step 1: Language Selection
Ask user to confirm their preferred language for:
- Internal thinking & system messages
- Conversation style
- File organization labels
Set this in USER.md under language_preference.
Step 2: File Initialization
- Copy template files from
templates/directory (if available) - Remove unused language variants from boilerplate
- Create skeleton folders for Knowledge Base (see KNOWLEDGE BASE ARCHITECTURE below)
- Clean up placeholder text from SOUL.md and USER.md
Step 3: User Profile Setup (Conversational, Not a Questionnaire)
Let the conversation flow naturally. Cover these topics, but weave them in:
- Role / Context: What does [Your Name] do? What's the main focus right now?
- Working Style: Pace, collaboration mode, decision-making patterns
- Goals for This System: What problems does this agent solve?
- Sensitive Zones: Any topics, directories, or types of work that need special handling?
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.
- 5d ago First seen · 499 lines · 4,330 tokens per session scan A 3bdf975ccf1f
memory-work CLAUDE.md is an instructions file published in the GitHub repository yiliqi78/memory-work (135 stars, last pushed 6mo ago), licensed MIT. It adds 4,330 tokens to every session, about $0.0216 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
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).