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/taichuy/agentmemory/agent-memorynpx skills add taichuy/agentMemory --skill agent-memorygit clone --depth 1 https://github.com/taichuy/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.00071 | $0.01097 |
| Opus 5 | $0.00036 | $0.00549 |
| Sonnet 5 | $0.00014 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
agent-memory 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Memory
Initialize the current project with the taichuy/agentMemory memory template. The goal is to make project memory available to coding agents without asking the user to paste the remote install command.
Workflow
-
Treat the current working directory as the target project unless the user gives another path.
-
Do not overwrite an existing
.memory/directory unless the user explicitly asks for force/overwrite. -
Prefer the bundled installer from this skill directory. Use the known skill path if the tool exposes it; otherwise try the global paths created by the installer:
python <skill-dir>/scripts/install-memory.py --dest . python "$HOME/.codex/skills/agent-memory/scripts/install-memory.py" --dest . python "$HOME/.claude/skills/agent-memory/scripts/install-memory.py" --dest . python "$HOME/.config/opencode/skills/agent-memory/scripts/install-memory.py" --dest . python "$HOME/.gemini/skills/agent-memory/scripts/install-memory.py" --dest .In Claude Code,
${CLAUDE_SKILL_DIR}may be used as<skill-dir>. Ifpythonis unavailable, trypython3orpy. If the user asked to replace an existing.memory/, add--force. -
If the bundled script cannot run, manually copy
assets/memory-template/.memoryinto the target project as.memory, then create or update these root files:AGENTS.mdCLAUDE.mdGEMINI.md
-
The root instruction files must contain this block, or an equivalent existing reference:
# 记忆 命中对应`记忆存储规则`自动更新对应记忆中 @.memory/AGENTS.md ## 用户偏好 @.memory/user-memory.md -
If a root instruction file already exists and already references
.memory/AGENTS.mdand.memory/user-memory.md, leave it unchanged. -
If a root instruction file exists but lacks the memory references, append the memory block instead of replacing the user's content.
-
Finish by reporting whether
.memory/was installed, kept, or replaced, and which instruction files were created or updated. -
Before ending the turn, infer the user's primary communication language from the current conversation and project files. Ask in that language whether to initialize
.memory/user-memory.md. Do not write user memory before the user confirms. -
If the user confirms, ask one compact initialization question group adapted to the project context. Include:
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 190 B
- assets/memory-template/.memory/AGENTS.md 6.6 KB
- assets/memory-template/.memory/feedback-memory/interaction/template.md 507 B
- assets/memory-template/.memory/feedback-memory/repository/template.md 512 B
- assets/memory-template/.memory/feedback-memory/template.md 881 B
- assets/memory-template/.memory/project-memory/template.md 648 B
- assets/memory-template/.memory/reference-memory/AGENTS.md 1.0 KB
- assets/memory-template/.memory/reference-memory/api-reference.md 695 B
- assets/memory-template/.memory/reference-memory/script-reference.md 633 B
- assets/memory-template/.memory/reference-memory/source-reference.md 636 B
- assets/memory-template/.memory/reference-memory/template.md 549 B
- assets/memory-template/.memory/todolist/template.md 492 B
- assets/memory-template/.memory/tool-memory/template.md 669 B
- assets/memory-template/.memory/user-memory.md 1023 B
- scripts/install-memory.py 4.2 KB runs code
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 · 82 lines · 71 tokens per session scan A 38640c20ecd6
agent-memory is a skill published in the GitHub repository taichuy/agentMemory (24 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,097 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…