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 derjochenmeyer/claude-code-craft --skill craft-project-remembergit clone --depth 1 https://github.com/derjochenmeyer/claude-code-craftWrote 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/derjochenmeyer/claude-code-craft/craft-project-remember)<a href="https://agentmods.dev/skills/derjochenmeyer/claude-code-craft/craft-project-remember"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-project-remember/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/derjochenmeyer/claude-code-craft/craft-project-remember"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-project-remember.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.00032 | $0.01012 |
| Opus 5.5 | $0.00013 | $0.00405 |
| Sonnet 5.5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
craft-project-remember 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-project-remember
Save something to project memory so future sessions can use it.
Invocation
/craft-project-remember-- Claude picks the most valuable insight from the current context/craft-project-remember [what]-- saves exactly what was specified
Memory structure
Target directory: .craft/memory/ in the current working directory.
.craft/memory/
INDEX.md index of all entries (one line per entry)
learned-rules.md lessons with L001 numbering (read by session-start hook)
YYYYMMDD_slug.md individual memory files
If .craft/memory/ does not exist: create it, create an empty MEMORY_INDEX.md, create an empty learned-rules.md.
Step 1: Determine what to save
If no argument was given: review the current conversation context and identify the most valuable non-obvious information. Prioritize: decisions > lessons > facts > context.
If an argument was given: use it as the content, enrich with context from the conversation if helpful.
Step 2: Classify
| Type | When to use |
|---|---|
fact |
Technical or domain knowledge not in the code itself |
decision |
A choice with rationale (why not the alternative?) |
lesson |
Something learned from a mistake, correction, or unexpected behavior |
context |
Background information future sessions might need |
warning |
Something easy to get wrong, with explanation |
Step 3: Check for duplicates
Read MEMORY_INDEX.md. If a similar entry already exists (same topic, overlapping keywords): update the existing file instead of creating a new one.
Step 4: Write the memory file
Filename: YYYYMMDD_slug.md -- today's date, slug derived from the title (lowercase, spaces to hyphens, max 40 characters).
Format:
---
title: [short title]
type: [fact | decision | lesson | context | warning]
date: YYYY-MM-DD
---
[Content -- precise, not verbose. 1-5 sentences.]
**Why:** [rationale or source, if applicable]
**How to apply:** [when/where this matters in future sessions]
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 · 133 lines · 32 tokens per session scan A 533903d2f322
craft-project-remember is a skill published in the GitHub repository derjochenmeyer/claude-code-craft (2 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,012 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn). Routes meetings to knowledge-meeting-ingest and short thoughts…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…