Claude-Mem, now presented as Grok Mem, records an agent's work, compresses it with AI, and brings relevant notes into later sessions so the agent can remember decisions and next steps. It is intended for persistent context across agent conversations and supports multiple coding-agent environments. The catalogue add-ons provide the workflows and integrations used to operate this memory system.
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 thedotmack/claude-mem --skill childhoodgit clone --depth 1 https://github.com/thedotmack/claude-memWrote 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/thedotmack/claude-mem/childhood)<a href="https://agentmods.dev/skills/thedotmack/claude-mem/childhood"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/childhood/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thedotmack/claude-mem/childhood"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/childhood.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.01113 |
| Opus 5.5 | $0.00020 | $0.00445 |
| Sonnet 5.5 | $0.00010 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
childhood 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 yesterday.
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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Childhood
Stay with a release after it ships. Verify what users receive and what production serves, then fix verified regressions within the user's authorized scope. A successful merge or publish command is the start of this work.
Establish the release
- Identify the repository, release version, immutable tag commit, merge commit, production deployment, and affected delivery surfaces. Use the release receipt and actual provider/registry state; do not guess from the current branch or today's latest build.
- Record the release, observation start/end, checks, findings, and next action with
work_state_writewhen available. Keep announcements and unrelated infrastructure failures distinguishable from product regressions. - Carry forward existing authorization. Monitoring does not itself authorize another release, rollback, production migration, or external announcement. Prepare and validate a concrete fix before requesting any authorization still missing.
Verify the delivered release
Choose the checks relevant to its delivery surfaces; independent checks can run in parallel.
| Surface | Evidence to collect |
|---|---|
| Source and CI | Confirm the tag resolves to the shipped commit. Inspect CI for that commit and any release/changelog commits, including late failures. Paginate new issue reports, merged-PR comments, reviews, and review threads since release; verify actionable reports against the shipped code. |
| Published package | Check the exact registry version and the intended distribution tag separately. Verify package hash, entry points, and required files in the downloaded artifact; run a small installed CLI smoke from an isolated directory. Preserve the command's actual exit code when filtering output. |
| Hosted service | Confirm the live production alias serves the intended deployment/commit. Check health and the changed user path through the real authenticated interface, plus relevant error signals. For schema changes, verify the normal migration ledger reports no pending migrations or drift. |
| Installed plugin | Discover the user's actual enabled registration/cache, not just the marketplace copy. Compare changed source/distribution artifacts and open a fresh tool connection. Compare the running worker's version/path to the enabled install; an updated cache can still talk to a stale process. Exercise the affected install/upgrade handoff where authorized. Check hooks or watcher configuration in their real project/runtime scope; label behavior you did not exercise as unverified. |
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.
- yesterday First seen · 47 lines · 49 tokens per session scan A d4f2db01f387
childhood is a skill published in the GitHub repository thedotmack/claude-mem (101,619 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,113 once invoked, about $0.0002 per session on Opus 5.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-10-18.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
git-story-film
Direct an animated film of about two minutes from a software repository's Git history. Select real commits, releases and reverts; develop the story, character and visual style; build an outline, cast sheet, storyboard and HTML review studio; then render a 4K/60fps MP4 after approval. Use for repository or product…