Memori hits 87% on LoCoMo at 721 tokens per query, 2.8% of full context, per README
Graphiti v0.31.1 tagged Oct 15. Temporal fact graphs with validity windows.
9 open-source GitHub repos for agent memory that survives sessions and keeps the prompt short:
212,966 stars. Pushed within 31 days. 6 Apache-2.0, 3 MIT. Oct 18.
EXTRACT WHAT MATTERS
01. mem0 ★67,374: https://t.co/WiO0IMQTUH -> extracts facts, recalls per user
02. langmem ★1,708: https://t.co/iIIeZ2SGmP -> agent learns from past chats
03. MemMachine ★3,073: https://t.co/2IRDjGetmh -> one store, any agent
04. memU ★14,554: https://t.co/HbadZV9AJN -> shared memory across agents
05. Memori ★17,151: https://t.co/HinrcYR31C -> chats into structured state
LINK IT IN A GRAPH
06. graphiti ★31,950: https://t.co/xRZyFjKlmA -> facts with validity windows
07. agent-memory ★585: https://t.co/MVsjHmSKak -> memory graph on Neo4j
RETRIEVE A SLICE
08. LightRAG ★40,200: https://t.co/yn7KG7XBTW -> graph retrieval, no heavy index
09. graphrag ★36,371: https://t.co/DgYEBR55Sc -> graph summaries for retrieval
turn → facts → graph → slice → call
pip install mem0ai
not more tokens. better recall ↓
FREE HECKING GOLD FOR ANY AI USER:
best 20 GitHub repos to make your own Reverse Engineering Crew to replicate any app you want
i wired these into opus 5.5 and it stopped being a chatbot.
it became a reversing crew:
[01] decompiler bridges: the agent drives the decompiler itself
- LaurieWired/GhidraMCP
- mrexodia/ida-pro-mcp
- fosdickio/binary_ninja_mcp
- radareorg/radare2-mcp
- cyberkaida/reverse-engineering-assistant
[02] ai copilots: explain, rename, comment inside your tool
- JusticeRage/Gepetto
- atredispartners/aidapal
- mahaloz/DAILA
- radareorg/r2ai
[03] runtime & mobile: debug and hook live processes
- AgentSmithers/x64dbgMCPServer
- signal-slot/mcp-gdb
- dnakov/frida-mcp
- zinja-coder/jadx-ai-mcp
- zinja-coder/apktool-mcp-server
[04] diff, decompile & fuzz: find what changed and prove the bug
- clearbluejar/ghidriff
- albertan017/LLM4Decompile
- google/oss-fuzz-gen
[05] benchmarks: check what the agent can really do
- andyzorigin/cybench
- NYU-LLM-CTF/NYU_CTF_Bench
- zhuyansen/awesome-ai-reverse-engineering
the flow: prompt -> mcp -> decompile -> debug -> patch -> verify
what i learned wiring this up:
- a smarter model doesn't win, the loop does.
- an agent that can only read pseudocode guesses.
- an agent that can also set a breakpoint, hook a function and diff two builds checks its own guesses.
that one change is what turns "AI explains code" into "AI does the reversing".
start with GhidraMCP + mcp-gdb. those two alone change how you work.
keep this for the next time a binary makes you want to quit.
i'm breaking down one of these setups end to end soon, so you'll want to be around for that.
and if you have a friend still reversing by hand at 2am, show them this.
be honest: would you trust an AI agent to patch a binary you ship?
nobody tells you this about grok bot
one guy spent a week reading everything about @bot: 600+ posts, 300 reels, 60 hours of video, the docs.
what he found:
> all your bots share ONE computer - same files, same cookies, same logins
> a 15-min routine = 96 runs a day. one hourly routine "can use a week of usage in a day"
> the terminal is a back door: type claude, log in your own Claude Code, drive it from your phone
plus 3 things xAI hid on purpose.
the full list, with every source, is in his article below 👇
OM NAMAH SHIVAY 🔱
H
A
R
H
A
R
M
A
H
A
D
E
V
OM NAMAH SHIVAY 🔱
H
A
R
H
A
R
M
A
H
A
D
E
V
OM NAMAH SHIVAY 🔱
H
A
R
H
A
R
M
A
H
A
D
E
V
OM NAMAH SHIVAY 🔱
H
A
R
H
A
R
M
A
H
A
D
E
V
OM NAMAH SHIVAY 🔱
H
A
R
H
A
R
M
A
H
A
D
E
V
@grok HAR HAR MAHADEV 🙌