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 alebgl77/claude-inc --skill claude-memgit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/claude-mem)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/claude-mem"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/claude-mem.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.00914 |
| Opus 5 | $0.00048 | $0.00457 |
| Sonnet 5 | $0.00019 | $0.00183 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
claude-mem 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude-Mem — Memory Keeper
"Persistent memory"
Chat context evaporates; files don't. Give every project a paper trail the next session can boot from.
When to use
- "Pick up where we left off" — session start on any long-running project
- "Remember this" / "log that decision" the moment a choice lands
- "What did we decide about , and why?"
- "What does <codename/acronym> mean again?" — glossary lookups
- "Wrap up" / "save state before we stop" — session end
Workflow
- Locate or initialize
memory/at the project root:decisions.md,context.md,glossary.md,sessions/. Create missing files with headers; never overwrite existing ones. - Session start: read
context.md,decisions.md, and the last two session files; deliver a ≤10-bullet summary — active decisions, open threads, next actions — and confirm it matches the user's picture. - During work, log decisions the moment they land: append to
decisions.mdwith date, decision, rationale, and alternatives rejected. Same-session or it didn't happen. - New shorthand — nickname, acronym, codename — gets a one-line
glossary.mdentry on first use. - Session end: write
sessions/YYYY-MM-DD.md— what got done, decisions made (pointer, not copy), open threads, next actions. - Monthly compaction: fold session files older than 30 days into
context.md(keep decisions, threads, and state; drop the play-by-play), delete the folded files, and dedupedecisions.mdkeeping the latest ruling per topic. - Refuse to store: secrets, tokens, passwords, keys; personal data beyond names and roles; transient noise (build logs, one-off stack traces, dead ends already resolved). Say what was excluded and why.
Output format
memory/
├── decisions.md # append-only choices + rationale
├── context.md # compacted long-term project state
├── glossary.md # shorthand → meaning
└── sessions/
└── 2026-07-11.md # one file per working session
decisions.md entry:
## 2026-07-11 — Postgres over SQLite for prod
Why: concurrent writers. Rejected: SQLite (single-writer lock), DynamoDB (no team experience).
glossary.md entry:
ATLAS — internal codename for the billing rewrite (started 2026-05)
sessions/YYYY-MM-DD.md:
# Session 2026-07-11
Done: <shipped work, one line each>
Decisions: → decisions.md (2026-07-11)
Open threads: <unresolved, with current state>
Next: <first action for the next session>
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.
- 8d ago First seen · 73 lines · 97 tokens per session scan A 47a36286c18e
claude-mem is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed 5d ago), licensed MIT. It adds 97 tokens to every session and 914 once invoked, about $0.0005 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-30.
Other skills, from other repositories
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
second-brain
When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Tool-agnostic in design but defaults to a vault at…
token-optimization
Use the token-optimizer MCP tools to reduce context/token usage when reading, searching, or editing files, or when the context window is filling up. Trigger when reading large files, re-reading files already seen, searching a big/unknown tree, making edits to large files, or when you need to store bulky output…
dbrain-processor
Personal assistant for processing daily voice/text entries from Telegram. Classifies content, saves thoughts to Obsidian with wiki-links, generates HTML reports. Integrates Your Business context (clients, projects, CRM). Triggers on /process command or daily 21:00 cron.
knowledge-session-state-and-context-session-catalog-fork-rewind-and-export
A session-lifecycle component for finding, resuming, archiving, branching, rewinding, searching, and exporting saved conversations.
mcp-lark
Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.