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/martian56/claude-engineer/project-memorynpx skills add martian56/claude-engineer --skill project-memorygit clone --depth 1 https://github.com/martian56/claude-engineerWrote 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/martian56/claude-engineer/project-memory)<a href="https://agentmods.dev/skills/martian56/claude-engineer/project-memory"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/project-memory.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.00050 | $0.00539 |
| Opus 5 | $0.00025 | $0.00269 |
| Sonnet 5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
project-memory 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 4d 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.
What it actually says
Project Memory
Announce at start: "I'm using claude-engineer:project-memory to keep durable project state."
Long autonomous builds outlive a single context window. Memory lives in files, not your head. The claude-engineer SessionStart hook auto-loads these at the start of every session.
The state files (in .claude-engineer/)
memory.md- durable project memory: key decisions (+ why), established conventions, the data model, open threads/risks, and "next action". The single source of truth for why things are the way they are.progress.md- the task ledger: each task with status (todo / doing / done), the commit/branch, and a one-line result. Append-only-ish; never delete history.current-phase.txt- one line naming the active phase (e.g.Phase 2 - Frontend).quality-gate-status.json- written by the project quality-gate runner; read by the commit gate. Do not hand-edit.
Iron Law
Trust the ledger and git log over your own recollection. After compaction, re-read these files before acting. Never re-run a task progress.md marks done.
When to update
- After every task: append a line to
progress.md. - On every non-obvious decision: add it to
memory.md(mirror big ones intodocs/plan/decisions.md). - On phase change: update
current-phase.txt.
Initialize (Phase 0 / planning)
Create .claude-engineer/ with seed memory.md (problem, stack, data model, decisions-so-far, next action), an empty progress.md ledger, and current-phase.txt. Add .claude-engineer/quality-gate-status.json to .gitignore (machine-generated); commit memory.md/progress.md so teammates and future sessions share them.
Red flags - STOP
- Starting work without reading
memory.md+progress.mdfirst. - A decision made in chat but never written down → write it now; chat is not durable.
- Re-deriving something already settled in
memory.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.
- 4d ago First seen · 34 lines · 50 tokens per session scan A 0765b4961343
project-memory is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 539 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
session-memory
Persist and recall findings across skill runs within and between sessions, building a cumulative knowledge base of what has been discovered about a design system. This is the cross-skill memory layer — it saves what was found, when, and by which skill, so future runs can compare, correlate, and avoid repeating work.…
settings
Configure agent settings — memory backend (builtin/QMD), search mode, temporal decay, citations. Triggers on /agent:settings, "configurar agente", "agent settings", "memory settings", "setup QMD", "configurar QMD", "configurar memoria".
heartbeat
Run agent heartbeat — periodic checks, memory consolidation, proactive work. Triggers on /agent:heartbeat, "heartbeat", "heartbeat check", "periodic check", "consolidar memoria".
new
Start a new session — save summary to memory, then mark as reset so next message gets a fresh greeting. OpenClaw-compatible. Triggers on /new, /reset, /agent:new, "nueva sesión", "new session", "reset".
compact
Flush important session context to daily log (manual memory flush). Does NOT invoke native /compact. Triggers on /compact, /agent:compact, /flush, "guarda memoria", "flush".
reflect
Per-project self-improvement - reads the .harness ledger and feedback memories, then proposes gated rule/threshold/ADR changes so the project stops repeating mistakes. Run periodically.