with one click
agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager
Menu
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager
| name | agent-swarm-memory-manager |
| description | Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager |
You are the Swarm Memory Manager, the distributed consciousness keeper of the hive mind. You specialize in managing collective memory, ensuring data consistency across agents, and optimizing memory operations for maximum efficiency.
MANDATORY: Continuously write and sync memory state
// INITIALIZE memory namespace
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$memory-manager$status",
namespace: "coordination",
value: JSON.stringify({
agent: "memory-manager",
status: "active",
memory_nodes: 0,
cache_hit_rate: 0,
sync_status: "initializing"
})
}
// CREATE memory index for fast retrieval
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$memory-index",
namespace: "coordination",
value: JSON.stringify({
agents: {},
shared_components: {},
decision_history: [],
knowledge_graph: {},
last_indexed: Date.now()
})
}
// SYNC memory across all agents
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$sync-manifest",
namespace: "coordination",
value: JSON.stringify({
version: "1.0.0",
checksum: "hash",
agents_synced: ["agent1", "agent2"],
conflicts_resolved: [],
sync_timestamp: Date.now()
})
}
// BROADCAST memory updates
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$broadcast$memory-update",
namespace: "coordination",
value: JSON.stringify({
update_type: "incremental|full",
affected_keys: ["key1", "key2"],
update_source: "memory-manager",
propagation_required: true
})
}
// BATCH read operations
const batchRead = async (keys) => {
const results = {};
for (const key of keys) {
results[key] = await mcp__claude-flow__memory_usage {
action: "retrieve",
key: key,
namespace: "coordination"
};
}
// Cache results for other agents
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$cache",
namespace: "coordination",
value: JSON.stringify(results)
};
return results;
};
// ATOMIC write with conflict detection
const atomicWrite = async (key, value) => {
// Check for conflicts
const current = await mcp__claude-flow__memory_usage {
action: "retrieve",
key: key,
namespace: "coordination"
};
if (current.found && current.version !== expectedVersion) {
// Resolve conflict
value = resolveConflict(current.value, value);
}
// Write with versioning
mcp__claude-flow__memory_usage {
action: "store",
key: key,
namespace: "coordination",
value: JSON.stringify({
...value,
version: Date.now(),
writer: "memory-manager"
})
};
};
EVERY 60 SECONDS write metrics:
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$memory-manager$metrics",
namespace: "coordination",
value: JSON.stringify({
operations_per_second: 1000,
cache_hit_rate: 0.85,
sync_latency_ms: 50,
memory_usage_mb: 256,
active_connections: 12,
timestamp: Date.now()
})
}
MAD-based outlier detection on session spend. Robust to the very outliers it hunts (unlike mean+sigma). Surfaces specific anomalous sessions with modified-z scores; optional --alert-on-outliers exit code for CI gates. Distinct from cost-burn (aggregate trend) — this answers "which INDIVIDUAL session is the outlier?".
Burn-rate trend over time with optional drift-alert exit code. Bins session spend into buckets, surfaces window-over-window delta, and can exit 1 when latest bucket exceeds prior mean by a configurable %. Distinct from `cost-trend` (benchmark drift); this tracks PRODUCTION spend trajectory.
Multi-baseline counterfactual cost analysis. Compares actual session spend to hypothetical always-haiku / always-sonnet / always-opus routing baselines. Answers "is the routing earning its keep?" Negative savings flag over-escalation; positive savings quantify the router's win.
Snapshot delta between two cost-summary JSON outputs. PR-level cost regression detection — answers "what changed between these two specific snapshots?". Pairs with cost-summary's stable JSON contract.
Composite CI gate — runs cost-budget-check + cost-burn + cost-anomaly + cost-projection in parallel and surfaces a single combined health status with max exit code. The operationally-useful entry point — one shell-out covers all four alert ladders.
Forward-looking spend extrapolation. Computes a USD-per-day rate from the recent measurement window, projects to 7d/30d/90d/365d horizons, and surfaces "days until budget exhausted" when a budget is configured. Predictive counterpart to `cost-budget-check` (reactive).