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 agentmods add skills/webzler/agentmemory/agentmemorynpx skills add webzler/agentMemory --skill agentmemorygit clone --depth 1 https://github.com/webzler/agentMemoryWhat 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 | $0.00018 | $0.00553 |
| Opus 5 | $0.00009 | $0.00277 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
agentMemory 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 2d 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.
This is a copy
86% identical to agent-memory — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentMemory Skill
This skill extends your capabilities by providing a persistent, searchable memory bank that automatically syncs with project documentation.
Prerequisites
- Node.js installed
- Check if
agentMemoryis already installed in the project:ls -la .agentMemory
Setup
-
Install Dependencies:
npm install -
Build the Project:
npm run compile -
Start the Memory Server: You need to run the MCP server to interact with the memory bank.
npm run start-server <project_id> <absolute_path_to_workspace>Note: This skill typically runs as a background process or via an mcp-server configuration. ensuring it is running is key.
Capabilities (MCP Tools)
Once the server is running, you can use these tools:
memory_search
Search for memories by query, type, or tags.
- Args:
query(string),type?(string),tags?(string[]) - Usage: "Find all authentication patterns" ->
memory_search({ query: "authentication", type: "pattern" })
memory_write
Record new knowledge or decisions.
- Args:
key(string),type(string),content(string),tags?(string[]) - Usage: "Save this architecture decision" ->
memory_write({ key: "auth-v1", type: "decision", content: "..." })
memory_read
Retrieve specific memory content by key.
- Args:
key(string) - Usage: "Get the auth design" ->
memory_read({ key: "auth-v1" })
memory_stats
View analytics on memory usage.
- Usage: "Show memory statistics" ->
memory_stats({})
Workflow
- Initialization: The first time you run this in a project, it may attempt to import existing markdown memory banks from
.kilocode/,.clinerules/, or.roo/. - Development Loop:
- Before Task: Search memory for relevant context.
- During Task: Use read/search to answer questions.
- After Task: Write new findings to memory.
- Sync: Your writes are automatically synced to standard markdown files in the project.
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.
- 2d ago First seen · 68 lines · 18 tokens per session scan A 17160641b60b
agentMemory is a skill published in the GitHub repository webzler/agentMemory (32 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to agent-memory, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
cognee-community
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify)…
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
ix
This skill should be used when answering structural questions about a codebase: understanding what a symbol is, tracing flows, measuring change impact, finding callers/callees/imports, or detecting code smells. It drives the Ix CLI (ix map/explain/trace/impact/search/rank/smells) against a persistent code graph stored…