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 XuanRanL/loamwright-SEO-Skill --skill memory-managergit clone --depth 1 https://github.com/XuanRanL/loamwright-SEO-SkillWrote 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/xuanranl/loamwright-seo-skill/memory-manager)<a href="https://agentmods.dev/skills/xuanranl/loamwright-seo-skill/memory-manager"><img src="https://agentmods.dev/badge/skills/xuanranl/loamwright-seo-skill/memory-manager/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/xuanranl/loamwright-seo-skill/memory-manager"><img src="https://agentmods.dev/badge/skills/xuanranl/loamwright-seo-skill/memory-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00464 |
| Opus 5 | $0.00022 | $0.00232 |
| Sonnet 5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
memory-manager 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 9d 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.
What it actually says
Memory Manager
Per seo-geo HOT/WARM/COLD pattern.
Memory layers
projects/{slug}/ ← Per-client (HOT/WARM)
├── business-context.json ← 90d TTL
├── research-cache/ ← 72h TTL
└── ...
memory/ ← Global (HOT/WARM/COLD)
├── entities/{id}.md ← Permanent (Wiki Phase 1/2/3)
├── wiki/ ← Phase 1/2/3 sediment
├── workspace/{task_id}/ ← HOT (current task)
└── learned-patterns.json ← Permanent (self-improvement)
Wiki Phase sedimentation
- Phase 1: Mention (1-2 articles cite entity)
- Phase 2: Established (3-9 cites; add 47 signals)
- Phase 3: Authority (10+ cites; full schema + ai_resolution probe weekly)
GDPR Art 17 (forget command)
/forget-project <slug>:
1. Move projects/{slug}/ → projects/.deleted/{slug}-{timestamp}/
2. Tombstone file with deleted_at timestamp
3. Schedule physical deletion in 30 days (per stop_finalize.py hook)
4. Memory/entities/: do NOT delete unless explicit (cross-project shared)
Workflows
HOT → WARM (task completion)
After Stage: final, workspace/{task} → memory/workspace/.archived/{YYYY-MM}/{task}/
WARM → COLD (90d expiry)
After 90d: projects/{slug}/business-context.json.freshness_state = "expired" → Suggest /init --refresh
Cleanup (stop_finalize hook)
- Archive completed tasks
- Purge .deleted projects >30d old
- Compact wiki entries that haven't been cited in 12 months
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.
- 9d ago First seen · 53 lines · 44 tokens per session scan A 2db025ab29d3
memory-manager is a skill published in the GitHub repository XuanRanL/loamwright-SEO-Skill (47 stars, last pushed 22d ago), licensed Apache-2.0. It adds 44 tokens to every session and 464 once invoked, about $0.0002 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
citedy-content-writer
From topic to published blog post in one conversation — generate SEO- and GEO-optimized articles with AI illustrations and voice-over in 55 languages, create social media adaptations for 9 platforms, set up automated content sessions, and manage product knowledge base. End-to-end blog autopilot. Powered by Citedy.
honcho
Configure and troubleshoot Honcho memory for Hermes.
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-cli
Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0…
mem0-remember
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
list-projects
Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.