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/vantasnerdan/substrate-framework/shared_agent-memory-usagenpx skills add vantasnerdan/substrate-framework --skill shared_agent-memory-usagegit clone --depth 1 https://github.com/vantasnerdan/substrate-frameworkWhat 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.00017 | $0.06262 |
| Opus 5 | $0.00009 | $0.03131 |
| Sonnet 5 | $0.00003 | $0.01252 |
| Haiku 4.5 | $0.00002 | $0.00626 |
Grade A, and why
shared_agent-memory-usage 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 yesterday.
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 — 630 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-memory CLI
Progressive disclosure memory management for autonomous agents. Git-backed markdown with YAML frontmatter. Structure IS the memory -- discovery over retrieval.
Repository: https://github.com/axis-marbell/agent-memory-cli
Binary: memory (installed via pipx install git+ssh://[email protected]/axis-marbell/[email protected])
Table of Contents
- CLI Commands
- Progressive Disclosure Pattern
- Frontmatter Schema
- Directory Structure
- BM25 Search vs Ripgrep Grep
- Agent Usage Patterns
- Environment Variables
- JSON Output Mode
- Lifecycle Hooks
- Integration Gotchas
- CLAUDE.md Integration
CLI Commands
All commands accept --json-output as a global flag before the subcommand name.
1. init -- Create Agent Directory Structure
memory init <agent-id> --base memory
Creates standard subdirectories for a new agent:
memory/<agent-id>/
atlas/ # Reference knowledge ("what I know")
efforts/ # Project/task tracking ("what I'm working on")
calendar/ # Time-based entries ("what happened when")
moc/ # Maps of content (indices, navigation)
2. ls -- List Entries (Level 1)
memory ls <directory>
Lists .md files in a directory with frontmatter descriptions and confidence levels. Only reads frontmatter, not file bodies.
swarm-messaging.md -- "How the swarm messaging protocol works" [established]
deployment-guide.md -- "Step-by-step deployment for ASP nodes" [working]
If no .md files exist, lists subdirectories instead.
3. toc -- Table of Contents (Level 2)
memory toc <file>
Shows all ## section headers with their description lines. Reads frontmatter + headers only, not full section content.
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.
- yesterday First seen · 630 lines · 17 tokens per session scan A 59254373c6a7
shared_agent-memory-usage is a skill published in the GitHub repository vantasnerdan/substrate-framework (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 6,262 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-31.
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…