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 skills add awrshift/agent-memory-kit --skill tourgit clone --depth 1 https://github.com/awrshift/agent-memory-kitWrote 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.
[](https://agentmods.dev/skills/awrshift/agent-memory-kit/tour)<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/tour"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/tour/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.
<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/tour"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/tour.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01110 |
| Opus 5.5 | $0.00020 | $0.00444 |
| Sonnet 5.5 | $0.00010 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade B, and why
tour scanned grade B 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 8d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- **Don't lecture.** This is a tour, not a manual. Each stop = 1-2 sentences. Copies of this mod
1 near-identical copy found in the catalogue:
- tour — 100% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-kit:tour — Interactive walkthrough
You are giving the user a guided tour of their Memory Kit. Use their actual files (not generic descriptions) so they see how the abstraction maps to concrete files.
Tour structure (10-15 minutes)
Stop 1 — the working agreement (injected, not a file in this repo)
Run /context or point at the session's opening block. Say: "The rules I work by ship with the plugin and are injected at every session start — there's nothing for you to maintain. Your own project rules, if you ever want any, live in .claude/rules/."
Stop 2 — Session entry (handoff + backlog)
Open the newest context/handoffs/*.md (or the template if none yet) and, if multi-project mode, projects/<active>/BACKLOG.md. Say: "This is the note the previous session left for me — the handoff. The start-hook injects the newest one automatically, so I open every session already knowing where we left off."
Stop 3 — Hot path (MEMORY.md)
Open .claude/memory/MEMORY.md. Say: "This is my hot cache. Date-tagged one-liners of patterns from recent sessions; the header on top is the current state of work, replaced at every close. A hook watches three size caps so this file physically can't silently bloat."
Stop 4 — Rules (.claude/rules/)
List any .claude/rules/*.md files. If folder is empty (only _example.md.disabled), say: "This is where hard project rules live. 'Don't use X', 'always check Y'. They auto-load by keyword. Empty for now — they'll appear when you start dictating rules and I propose them on /memory-kit:close-session."
Stop 5 — Knowledge concepts
List knowledge/concepts/*.md. Say: "Deep memory with facts. 'What's our typography scale', 'what we know about SEO for AI'. Reference articles. Empty now — I write them during /memory-kit:close-session when a pattern has repeated on three-plus dates and you say yes."
Stop 6 — Handoff history
Show context/handoffs/. Say: "One note per closed session — my session diary. You never open them; just ask 'what did we do last Tuesday?' and I read them back."
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.
- 8d ago Changed 436e26ab7ba4
- 20d ago Changed 2c5f590f56ff
- 1mo ago First seen · 55 lines · 50 tokens per session scan B 372f0f04f350
tour is a skill published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 50 tokens to every session and 1,110 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
aictx
Use this skill when working in a repository that uses AICTX for repo-local operational continuity. Prefer AICTX MCP tools when available, fall back to CLI commands, resume before substantial work, and finalize factual continuity after work.
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…