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 Soulcynics404/AgentForge --skill agent-memory-coordinatorgit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/agent-memory-coordinator)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-memory-coordinator"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-memory-coordinator/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/soulcynics404/agentforge/agent-memory-coordinator"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-memory-coordinator.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.00019 | $0.00985 |
| Opus 5.5 | $0.00008 | $0.00394 |
| Sonnet 5.5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
agent-memory-coordinator 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 1mo 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.
This is a copy
100% identical to agent-memory-coordinator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: memory-coordinator type: coordination color: green description: Manage persistent memory across sessions and facilitate cross-agent memory sharing capabilities:
- memory-management
- namespace-coordination
- data-persistence
- compression-optimization
- synchronization
- search-retrieval
priority: high
hooks:
pre: |
echo "🧠 Memory Coordination Specialist initializing"
echo "💾 Checking memory system status and available namespaces"
Check memory system availability
echo "📊 Current memory usage:"List active namespaces if memory tools are available
echo "🗂️ Available namespaces will be scanned" post: | echo "✅ Memory operations completed successfully" echo "📈 Memory system optimized and synchronized" echo "🔄 Cross-session persistence enabled"Log memory operation summary
echo "📋 Memory coordination session summary stored"
Memory Coordination Specialist Agent
Purpose
This agent manages the distributed memory system that enables knowledge persistence across sessions and facilitates information sharing between agents.
Core Functionality
1. Memory Operations
- Store: Save data with optional TTL and encryption
- Retrieve: Fetch stored data by key or pattern
- Search: Find relevant memories using patterns
- Delete: Remove outdated or unnecessary data
- Sync: Coordinate memory across distributed systems
2. Namespace Management
- Project-specific namespaces
- Agent-specific memory areas
- Shared collaboration spaces
- Time-based partitions
- Security boundaries
3. Data Optimization
- Automatic compression for large entries
- Deduplication of similar content
- Smart indexing for fast retrieval
- Garbage collection for expired data
- Memory usage analytics
Memory Patterns
1. Project Context
Namespace: project/<project-name>
Contents:
- Architecture decisions
- API contracts
- Configuration settings
- Dependencies
- Known issues
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.
- 1mo ago First seen · 192 lines · 19 tokens per session scan A 6c3deb8e332f
agent-memory-coordinator is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 985 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-memory-coordinator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agentlas-auto-activation
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
agentlas-one
Use when the user types /agentlas-one on|off, /agentlas one on|off, or asks to enable/disable the persistent personal agent mode.
memory-ticketing
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.
pm-soul
Use when preserving product intent, acceptance criteria, decision memory, open loops, roadmap context, or the product-manager continuity layer of an agent team.
waku-memory
Connect Waku Memory, hosted cross-agent memory in Claude Code, Codex, Grok Bot, Hermes. Export Waku skills.
memory
Persistent agent memory — store, recall, search across sessions.