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/b1rdmania/ghostclaw/migrate-memorynpx skills add b1rdmania/ghostclaw --skill migrate-memorygit clone --depth 1 https://github.com/b1rdmania/ghostclawWhat 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.00036 | $0.01114 |
| Opus 5 | $0.00018 | $0.00557 |
| Sonnet 5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade C, and why
migrate-memory scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- To revert: `cp CLAUDE.md.backup CLAUDE.md && rm -rf memory/` How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Memory
Migrates an existing GhostClaw group from the single-file CLAUDE.md memory system to the structured three-file system.
What it does
- Backs up the current
CLAUDE.mdtoCLAUDE.md.backup - Creates
memory/identity.md— extracts soul, personality, user info - Creates
memory/state.md— extracts project status, current work - Creates
memory/log.md— empty, ready for the agent to start logging - Rewrites
CLAUDE.mdto be instructions-only (no project data)
Steps
1. Identify the group folder
Ask the user which group to migrate, or default to the main group:
GROUP_DIR="$GHOSTCLAW_GROUP_DIR"
2. Back up
cp "$GROUP_DIR/CLAUDE.md" "$GROUP_DIR/CLAUDE.md.backup"
3. Read the existing CLAUDE.md
Read the full file. Identify these sections:
- Soul/personality — voice, tone, communication style
- About the user — name, location, projects, key people
- About the agent — name, machine, accounts, capabilities
- Project status — active projects, parked projects, shipped work
- Admin/technical — file paths, IPC, scheduling, group management
4. Create memory/identity.md
Extract soul + user info + agent info into this structure:
# Identity
## Soul
[paste soul/personality section]
## About the User
[paste user details]
## About Me
[paste agent details — name, machine, accounts]
5. Create memory/state.md
Extract project status into this structure:
# Current State
Last updated: [today's date]
## Active Projects
[active projects with current status]
## Parked
[inactive/shipped projects]
## Recent Decisions
[leave empty — agent will start populating this]
6. Create memory/log.md
# Log
Append-only. Most recent first. Never edit old entries — only prepend new ones.
---
## [today's date]
- Migrated to three-file memory system (identity + state + log)
7. Rewrite CLAUDE.md
Replace the CLAUDE.md with the instructions-only template from .claude/skills/setup-ghostclaw/templates/CLAUDE.md.
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.
- 3d ago First seen · 161 lines · 36 tokens per session scan C 13dc0b5e1189
migrate-memory is a skill published in the GitHub repository b1rdmania/ghostclaw (91 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,114 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
lobu-operator
Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.
company-agent-infrastructure
Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…
lobu-builder
Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…
crm-ops
How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.
deliveroo-order
Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…
lobu
Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.