setup-memory

setup-memory is a skill for Claude Code from Abilityai/abilities. It costs 11 tokens per session (778 once invoked), scanned A, original, MIT.

A setup procedure for a JSON-based memory system that stores an agent’s profile, preferences, facts, decisions, project notes, and recent activity. JSON is a structured text format commonly used for storing data.

In plain words
What is it for?
Choosing the memory type, creating the memory directory and index, and optionally recording an action history.
Why use it?
It creates a consistent place for information that should remain available across interactions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Part of the agent-dev plugin — 47 skills shipped together

Good fit Choosing the memory type, creating the memory directory and index, and optionally recording an action history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/abilityai/abilities/setup-memory
Install

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.

Any agent
npx skills add Abilityai/abilities --skill setup-memory
Clone the repo
git clone --depth 1 https://github.com/Abilityai/abilities

Made for: Claude Code.

Or install agent-dev, the plugin that ships this one along with the rest of its 47 skills.

Wrote 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.

agentmods badge for setup-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/abilityai/abilities/setup-memory/github.svg)](https://agentmods.dev/skills/abilityai/abilities/setup-memory)
Your own site
<a href="https://agentmods.dev/skills/abilityai/abilities/setup-memory"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/setup-memory/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.

agentmods 80×15 button for setup-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/abilityai/abilities/setup-memory"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/setup-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 778 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00778
Opus 5.5 $0.00004 $0.00311
Sonnet 5.5 $0.00002 $0.00156
Haiku 4.5 $0.00001 $0.00078

Measured 1mo ago against content hash b9fda2bf9057, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-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 1mo 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.

plugins/agent-dev/memory-templates/json-state/setup-memory/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Setup JSON Memory

Initialize a structured JSON memory system for persistent agent state.

Step 1: Ask Configuration

Use AskUserQuestion:

Question 1: "What type of agent is this memory for?"

  • Options:
    • "Business assistant" - Profile, entities, tasks focus
    • "Personal assistant" - Preferences, reminders focus
    • "Technical agent" - Context, project tracking focus
    • "General purpose (Recommended)" - All sections

Question 2: "Should the memory track action history?"

  • Options:
    • "Yes (Recommended)" - Creates action_log.txt
    • "No" - Memory only, no action log

Step 2: Create Directory Structure

mkdir -p memory

Step 3: Create Memory Index

Write memory/memory_index.json:

{
  "metadata": {
    "schema_version": "1.0",
    "created": "[ISO timestamp]",
    "last_updated": "[ISO timestamp]",
    "total_interactions": 0
  },
  "profile": {
    "name": null,
    "role": null,
    "context": null
  },
  "preferences": {
    "communication_style": null,
    "tools": []
  },
  "memory": {
    "key_facts": [],
    "decisions": [],
    "project_overviews": []
  },
  "context": {
    "active_topics": [],
    "recent_work": [],
    "scratchpad": null
  },
  "entities": [],
  "tasks": {
    "active": [],
    "completed": []
  },
  "custom": {}
}

Step 4: Create Action Log (if enabled)

Write memory/action_log.txt:

# Action Log
# Format: YYYY-MM-DD HH:MM:SS - Action description
# Newest entries at top

[ISO timestamp] - Memory system initialized

Step 5: Create Memory Map

Write memory/memory_map.yaml:

# Memory System Map
# High-signal index of memory components

memory_index:
  path: memory/memory_index.json
  load: selective  # Use jq queries, not full load
  sections:
    - profile
    - preferences
    - context
    - entities

action_log:
  path: memory/action_log.txt
  load_lines: 50  # Most recent entries

custom_files: []

Step 6: Update CLAUDE.md

Add memory configuration:

## Memory System

JSON-based persistent memory in `memory/` folder.

### Loading Memory
Use `/load-memory` to load context at session start.
Load selectively - don't read entire memory_index.json.

### Updating Memory
Use `/memory-jq` for efficient field updates.
Use `/update-memory` after significant changes.

### Memory Sections
- `profile` - User/agent identity
- `preferences` - Settings and styles
- `memory.key_facts` - Important facts to remember
- `context` - Current work state
- `entities` - People, projects, orgs
- `tasks` - Active and completed items

### Action Log
`memory/action_log.txt` - Reverse chronological action history.
Newest entries at top. Load last 50 lines for context.

Read the full file on GitHub · 146 lines

Changes

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.

  1. 1mo ago First seen · 146 lines · 11 tokens per session scan A b9fda2bf9057

Subscribe to this mod's changes

setup-memory is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 778 once invoked, about $0.0000 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-08-30.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

forget

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…

asgeirtj/system_prompts_leaks · 74 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

shellm

Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.

laude-institute/headlong · 49 tokens