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 skills add sefaertunc/Worclaude --skill memory-architecturegit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/skills/sefaertunc/worclaude/memory-architecture)<a href="https://agentmods.dev/skills/sefaertunc/worclaude/memory-architecture"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/memory-architecture/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/skills/sefaertunc/worclaude/memory-architecture"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/memory-architecture.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.00019 | $0.01574 |
| Opus 5.5 | $0.00008 | $0.00630 |
| Sonnet 5.5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
memory-architecture 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Architecture
Worclaude projects use five distinct memory layers. Each has a different scope, owner, and lifecycle. Routing a fact to the correct layer is a load-bearing decision — the wrong layer means the fact is invisible when needed, or noisy when not.
The Five Layers
| Layer | Scope | Owner | Lifecycle |
|---|---|---|---|
CLAUDE.md |
Team | Manual (humans + Claude via /update-claude-md) |
Stable, lean (target ~200 lines) |
.claude/rules/ |
Team | Manual, topic-organized | Stable; optionally path-scoped (deferred — see BACKLOG) |
.claude/learnings/ |
Team | Hook-captured (learn-capture.cjs) |
Append-only; transient inputs to promotion |
CLAUDE.local.md |
Personal | Manual; gitignored | Per-machine sandbox; never shared |
| Claude Code auto memory | Personal | Autonomous (Claude) | Active, self-pruning |
The line between team and personal is the most important boundary. Team layers are committed and shared with collaborators; personal layers stay on the local machine.
Routing Contract
When a fact, rule, or pattern surfaces during a session, route it like this:
| Source | Destination |
|---|---|
A team-relevant rule the user wants enforced — typed [LEARN] block or /learn invocation |
.claude/learnings/<category>.md (via hook) |
| A personal preference (workflow, tone, naming whim) | Claude Code auto memory (Claude does this autonomously when noticed) |
| A machine-local sandbox value (paths, secrets, dev URLs) | CLAUDE.local.md (manual; gitignored) |
| A topic that has accreted multiple learnings AND is stable | Promote to CLAUDE.md via /update-claude-md |
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.
- 1mo ago First seen · 116 lines · 19 tokens per session scan A 3ee1cdc2f825
memory-architecture is a skill published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,574 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory CLI for Hermes Agent. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…