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/ilyagorsky/memory-toolkit/memory-setupnpx skills add IlyaGorsky/memory-toolkit --skill memory-setupgit clone --depth 1 https://github.com/IlyaGorsky/memory-toolkitWhat 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.00020 | $0.02685 |
| Opus 5 | $0.00010 | $0.01342 |
| Sonnet 5 | $0.00004 | $0.00537 |
| Haiku 4.5 | $0.00002 | $0.00268 |
Grade A, and why
memory-setup 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-setup — Initialize or upgrade project memory
Detects existing memory, adds what's missing, doesn't overwrite anything.
Step 1: Find memory directory
GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
PROJ_KEY=$(echo "$GIT_ROOT" | tr '/.' '-' | sed 's/^-//')
MEM_DIR="$HOME/.claude/projects/-${PROJ_KEY}/memory"
Check what already exists:
echo "=== Memory dir: $MEM_DIR ==="
[ -d "$MEM_DIR" ] && echo "DIR: exists" || echo "DIR: missing"
[ -f "$MEM_DIR/MEMORY.md" ] && echo "MEMORY.md: exists" || echo "MEMORY.md: missing"
[ -f "$MEM_DIR/memory.js" ] && echo "memory.js: exists" || echo "memory.js: missing"
[ -f "$MEM_DIR/workstreams.json" ] && echo "workstreams.json: exists" || echo "workstreams.json: missing"
ls "$MEM_DIR"/*.md 2>/dev/null | wc -l | xargs -I{} echo "MD files: {}"
ls -d "$MEM_DIR"/*/ 2>/dev/null | wc -l | xargs -I{} echo "Subdirs: {}"
Report findings to the user before making any changes.
Step 2: Branch by state
A) No memory dir at all → fresh setup
If --fresh argument or no $MEM_DIR:
Before creating anything, show the user what will be set up:
Fresh memory setup for this project:
Dir: {MEM_DIR}
Will create: MEMORY.md, workstreams.json, memory-schema.json
Subdirs: feedback/, decisions/, profile/, reference/, notes/, workstreams/
Will ask: workstreams, role, language, key links
Proceed? (yes/skip)
Wait for confirmation before creating any files.
mkdir -p "$MEM_DIR"- If no
CLAUDE_PLUGIN_ROOT:cp /path/to/memory-toolkit/scripts/memory.js "$MEM_DIR/" - Ask: "What are the main workstreams in this project?" → create
workstreams.json - Profile interview → create
profile/user-role.md(frontmattertype: user). Ask sequentially, accept short answers, skip empty:- Role: "What's your role and team?" (job title, company, team size)
- Initiative: "What's the broader initiative or goal you're driving here?"
- Communication style: "Anything about how you like to work? (pacing, directness, things that annoy you)"
- Domain terminology: "Any project-specific terms I should know? (e.g. портфель instead of sprint, custom SP units)"
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 · 316 lines · 20 tokens per session scan A 14fcf8cf8fe3
memory-setup is a skill published in the GitHub repository IlyaGorsky/memory-toolkit (13 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 2,685 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
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
math-unicode
Use when a response needs mathematical notation (equations, filters, set-builder notation, statistics, calculus, linear algebra, logic, ratios, drops, counts) and the output goes to a terminal or TUI that cannot render LaTeX: Claude Code, Codex CLI, SSH and tmux sessions, CI logs. Load it before composing, including…
vibe-ship
Generates a complete, production-ready deployment setup for any app in one pass -- Dockerfile, docker-compose.yml, .dockerignore, CI/CD (GitHub Actions), scalability config (health checks, resource limits, K8s on request), and security hardening (non-root user, secrets, dependency scanning). Auto-detects the stack…
anatomia-cc
ES: Te dice qué construir en Claude Code y te da el esqueleto de archivos: skill y en qué modo, subagente, hook, servidor MCP, plugin, rutina, artefacto, app con el Agent SDK, una línea en CLAUDE.md, o nada. Corré esto antes del primer archivo. Se dispara con «esto lo hago como skill o como agente», «necesito un MCP o…
create-agents-md
Create concise, repository-specific AGENTS.md files with operational contract, precedence rules, and drift-control guidance.
create-checkpoint
Capture the current session state as a checkpoint artifact per spec section 4.4. Use when the user signals session end or explicitly requests a checkpoint. Do not use mid-session or without user approval.