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 skills/d2a8k3u/claude-code-memory/memory-initnpx skills add d2a8k3u/claude-code-memory --skill memory-initgit clone --depth 1 https://github.com/d2a8k3u/claude-code-memoryWhat 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.00061 | $0.00982 |
| Opus 5 | $0.00030 | $0.00491 |
| Sonnet 5 | $0.00012 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
memory-init 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Memory Bootstrap
Scan the current project and populate the memory with foundational knowledge. This gives Claude an informed starting point instead of beginning from scratch.
Discovery Steps
Perform these steps in order. For each step, read the relevant files, extract key information, and store it using memory_store or memory_store_batch.
1. Project Identity
Look for and read:
CLAUDE.md,.claude/CLAUDE.md,.claude/settings.jsonREADME.md,READMEpackage.json,Cargo.toml,pyproject.toml,go.mod,Gemfile,pom.xml,build.gradle
Store as semantic memories with titles:
- Project name and description
- Programming language(s) and framework(s)
- Key dependencies and their purposes
- Version requirements
2. Project Structure
Run a directory listing (top 2-3 levels) and analyze the layout.
Store as semantic memories with titles:
- High-level architecture (monorepo, monolith, microservices, etc.)
- Key directories and their purposes
- Entry points and main modules
3. Build, Test & Run
Look for and read:
package.jsonscripts sectionMakefile,Taskfile.yml,justfileDockerfile,docker-compose.yml- CI configs:
.github/workflows/,.gitlab-ci.yml,Jenkinsfile
Store as procedural memories:
- How to install dependencies
- How to build the project
- How to run tests
- How to start the dev server
- How to deploy (if CI config is present)
4. Conventions & Patterns
Look for and read:
CLAUDE.md(coding conventions, rules).eslintrc,.prettierrc,biome.json,ruff.tomltsconfig.json,.editorconfig.env.example,.env.template
Store as pattern memories with titles:
- Code style conventions (formatting, naming)
- Linting rules and their rationale
- Environment variables and their purposes
- TypeScript/compiler configuration choices
5. Architecture Decisions
Look for and read:
CLAUDE.md(architectural notes)docs/,ADR/,architecture/directories- README sections about architecture
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.
- 2d ago First seen · 118 lines · 61 tokens per session scan A 92e23434bbfb
memory-init is a skill published in the GitHub repository d2a8k3u/claude-code-memory (7 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 982 once invoked, about $0.0003 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 skills, from other repositories
memory-assistant
Comprehensive memory management skill that guides memory capture and recall throughout sessions. Triggers when: user makes architectural decisions ("let's use", "we should", "decided to", "choosing"), discovers learnings ("TIL", "learned that", "discovered", "found out", "realized"), encounters blockers ("stuck on"…
memory-recall
This skill should be used when the user asks about "past decisions", "previous learnings", "what did we decide", "how did we solve", "remember when", or mentions topics that may have stored memories. Also triggers when working on tasks where historical context would be valuable, such as "working on authentication"…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.