memory — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited memory (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Operate on .claude/memory/. Memory persists across sessions and is shared across all 12 toolkit agents.
list (default)Print the current memory index, grouped by type. One line per entry: name, description, last-verified date.
## Project (4)
- monorepo-layout — apps/, packages/, infra/. Yarn workspaces. (2026-04-18)
- billing-flag-state — webhook still off in prod, on in staging. (2026-05-01)
- migration-plan-q3 — auth migration to Lucia, target 2026-07-01. (2026-04-30)
…
## User (2)
- role — senior eng, owns the platform team. (2026-04-15)
- preferences — terse responses; no emojis; vitest over jest. (2026-04-15)
## Feedback (1)
- no-mocks-in-integration — integration tests must hit real DB. (2026-04-22)
## Reference (1)
- linear-eng-board — pipeline bugs tracked in Linear project ENG. (2026-04-15)
## Inherited (0)
## Handoffs (3)
- 2026-05-01 — auth migration shipped; billing flag pending.
- 2026-04-30 — design system v2 RFC opened.
- 2026-04-29 — initial repo onboarding.search <query>Find memories whose name, description, or body matches the query. Use to remind yourself of context before answering a related question.
saveWalk through writing a new memory:
project/ and feedback/, prompt for Why: and How to apply: explicitly..claude/memory/MEMORY.md index.Frontmatter:
---
name: <title>
type: project | user | feedback | reference
description: <one-line>
created: 2026-05-02
last-verified: 2026-05-02
---
<body>update <name>Find the memory by name. Show its current contents. Ask what to change. Update the file and bump last-verified.
delete <name>Find the memory. Show what would be deleted. Ask for confirmation. Delete the file and remove the line from MEMORY.md.
dedupeScan memories within each type for likely duplicates (same topic phrased differently). Surface candidates. Never auto-merge — always show pairs and ask which to keep.
memory-discipline rule)MEMORY.md index when adding/removing.For list, render the grouped index above. For search, show matching memories with their full body. For save / update / delete, show before/after diffs and confirm before writing.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.