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/abilityai/abilities/add-memorynpx skills add Abilityai/abilities --skill add-memorygit clone --depth 1 https://github.com/Abilityai/abilitiesWhat 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.00024 | $0.01263 |
| Opus 5 | $0.00012 | $0.00632 |
| Sonnet 5 | $0.00005 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
add-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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Memory
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.add-memory vX.Y — recent: <summary>. Then proceed.
Add a memory system to an existing agent. Memory skills are COPIED into the agent's .claude/skills/ directory — the agent becomes self-contained with no plugin dependency.
Memory Types
| Type | Description | Skills Installed |
|---|---|---|
| file-index | File system awareness — creates and maintains a searchable file index | setup-index, refresh-index, search-files |
| brain | Zettelkasten-style knowledge graph — atomic notes with connections | setup-brain, create-note, search-brain, find-connections |
| json-state | Structured JSON state with jq-based updates and action logging | setup-memory, load-memory, update-memory, memory-jq |
| workspace | Multi-session project tracking — organized folders, sessions, archives | setup-projects, create-project, create-session, archive-project |
Process
Step 1: Determine Agent Directory
Check if we're in an agent directory (has CLAUDE.md) or if user specified a path.
# Check current directory
if [ -f "CLAUDE.md" ]; then
AGENT_DIR="$(pwd)"
else
# Ask user for agent path
fi
If no CLAUDE.md found, ask:
- Question: "What agent should I add memory to?"
- Hint: "Enter the path to the agent directory (should contain CLAUDE.md)"
Step 2: Check Argument or Ask Memory Type
If user provided an argument (e.g., /agent-dev:add-memory brain), use that.
Otherwise, use AskUserQuestion:
-
Question: "What kind of memory does this agent need?"
-
Header: "Add Memory"
-
Options:
-
File awareness (file-index) — "I need the agent aware of workspace files"
- Creates a searchable index of files in the workspace
- Good for: agents that need to find and reference files
-
Knowledge graph (brain) — "I need connected notes, evolving knowledge"
- Zettelkasten-style atomic notes with connections
- Good for: research agents, knowledge management, idea linking
-
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 · 138 lines · 24 tokens per session scan A 0fff8cfe502f
add-memory is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 1,263 once invoked, about $0.0001 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.
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…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…