hooks-a48aec — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited hooks-a48aec (Hook) 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.
<div align="center">
<img src="logo.png" alt="Claude Brain" width="320" />
<br />
https://github.com/user-attachments/assets/b57cb3db-576b-4c1f-af92-95796ba3fb5b
<br />
[Install in 30 seconds](#installation) · How it Works · Commands · Full Demo
</div>
<br />
You: "Remember that auth bug we fixed?"
Claude: "I don't have memory of previous conversations."
You: "We spent 3 hours on it yesterday"
Claude: "I'd be happy to help debug from scratch!"200K context window. Zero memory between sessions.
You're paying for a goldfish with a PhD.
<br />
You: "What did we decide about auth?"
Claude: "We chose JWT over sessions for your microservices.
The refresh token issue - here's exactly what we fixed..."One file. Claude remembers everything.
<br />
# One-time setup (if you haven't used GitHub plugins before)
git config --global url."https://github.com/".insteadOf "[email protected]:"# In Claude Code
/plugin add marketplace memvid/claude-brainThen: /plugins → Installed → mind Enable Plugin → Restart.
Done.
<br />
After install, Claude's memory lives in one file:
your-project/
└── .claude/
└── mind.mv2 # Claude's brain. That's it.No database. No cloud. No API keys.
What gets captured:
Why one file?
git commit → version control Claude's brainscp → transfer anywhere<br />
In Claude Code:
/mind stats # memory statistics
/mind search "authentication" # find past context
/mind ask "why did we choose X?" # ask your memory
/mind recent # what happened latelyOr just ask naturally: "mind stats", "search my memory for auth bugs", etc.
<br />
For power users who want direct access to their memory file:
npm install -g memvid-climemvid stats .claude/mind.mv2 # view memory stats
memvid find .claude/mind.mv2 "auth" # search memories
memvid ask .claude/mind.mv2 "why JWT?" # ask questions
memvid timeline .claude/mind.mv2 # view timeline<br />
<details> <summary><b>How big is the file?</b></summary>
Empty: ~70KB. Grows ~1KB per memory. A year of use stays under 5MB.
</details>
<details> <summary><b>Is it private?</b></summary>
100% local. Nothing leaves your machine. Ever.
</details>
<details> <summary><b>How fast?</b></summary>
Sub-millisecond. Native Rust core. Searches 10K+ memories in <1ms.
</details>
<details> <summary><b>Reset memory?</b></summary>
rm .claude/mind.mv2
</details>
<br />
<div align="center">
Built on [memvid](https://github.com/memvid/memvid) - the single-file memory engine
<br />
If this saved you time, [star the repo](https://github.com/memvid/claude-brain)
<br />
Send me your `.mv2` file and I'll tell you what's wrong with your code. No context needed - I already know everything.
</div>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.